You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 18, 2019. It is now read-only.
I am having a similar issue while running python setup.py test. I get the following two errors:
It seems like the first error is the same as that brought up by Roger-Luo. I know that this module is still in progress, so I wonder if the test is not necessarily supposed to be passed yet. Thank you for making this module and for any suggestions.
===================================================================
ERROR: test (unittest.loader._FailedTest)
----------------------------------------------------------------------
ImportError: Failed to import test module: test
Traceback (most recent call last):
File "/usr/lib/python3.5/unittest/loader.py", line 428, in _find_test_path
module = self._get_module_from_name(name)
File "/usr/lib/python3.5/unittest/loader.py", line 369, in _get_module_from_name
__import__(name)
File "/mnt/c/Users/HP/Documents/Quantum_Machine_Learning_Research/QuantaLearn/pytorch-complex-master/test.py", line 7, in <module>
2j * a
TypeError: mul(): argument 'other' (position 1) must be Tensor, not complex
===================================================================
ERROR: test_scalar_binary_op (tests.test_tensor.TestComplexTensor)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/mnt/c/Users/HP/Documents/Quantum_Machine_Learning_Research/QuantaLearn/pytorch-complex-master/tests/test_tensor.py", line 22, in test_scalar_binary_op
2 * a
RuntimeError: _th_tensor is not implemented for type CPUComplexType<double>
----------------------------------------------------------------------
This package is WIP, and requires a lot effort. It would be great if people could collaborate on this. As what's already in README, nothing is guaranteed to work... and you shouldn't use this for certain task unless you know what's happening.
BTW It will be great if you could use markdown format next time..
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The text was updated successfully, but these errors were encountered: