Skip to content
New issue

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

Change of Tracer changes the results #64

Open
nabobalis opened this issue Jul 24, 2024 · 2 comments
Open

Change of Tracer changes the results #64

nabobalis opened this issue Jul 24, 2024 · 2 comments

Comments

@nabobalis
Copy link
Contributor

nabobalis commented Jul 24, 2024

Describe the bug

For tests:

  • test_field_line_polarity
  • test_footpoints

If you replace the Python Tracer with the one from StreamTracer, the polarity and the number of solar_footpoint change breaking both tests.

On the surface I would expect both traces to give the same output.

Question is, do older version of streamtracer agree or not
Also is this a problem? Should they give the same output?

@STBadman
Copy link
Contributor

i'll look into this - it seems possible there could be some differences from numerical issues if the discretization is different between the tracers, but a big change like a reversed polarity is surprising to me at first.

@nabobalis
Copy link
Contributor Author

nabobalis commented Jul 25, 2024

It it possible its just an artifact of the way the test is setup.

I did try streamtracer from 2.0 to 2.2 and they all had the same result.
I just tried the FORTRAN version (1.2.0), that's the same as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants