We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Here I report some (apparently) weird behaviors I caught while writing the code.
In OpticsNumerical
OpticsNumerical
Left is wrong, right is ok
Yellow = rx = ok grey = sx = wrong
I have no ideas (perhaps try is very strict and it catches warning, too?).
try
Action: I revert to RX version.
The text was updated successfully, but these errors were encountered:
LX: wrong RX: Correct
Screenshot of the error, with LX
Comment: it must be some stupid "boundary error" (points are 10000, returned are 9999)
In any case, if I geld XProp I should also take care of what is happening to other vectors (which will be made up of \tilde(N) points and not N).
XProp
Sorry, something went wrong.
We decided that this is not a priority as OASYS is stuck to a previous version of python.
Compativility with Python> 3.7 COULD BE RELEVANT when using LibWiser only, but this is not a priority now.
No branches or pull requests
Here I report some (apparently) weird behaviors I caught while writing the code.
In
OpticsNumerical
Left is wrong, right is ok
Yellow = rx = ok
grey = sx = wrong
I have no ideas (perhaps
try
is very strict and it catches warning, too?).Action: I revert to RX version.
The text was updated successfully, but these errors were encountered: