-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Some documentation could do with a quick update #35
Comments
So this doc references If so (if the version affects the tracing backend language) - then should we rename the class PerfomanceTracer or something similar? or if Fortran support is going away entirely, rename it RustTracer ? |
That's also my understanding.
That's why I added "Automatically pick working/best Tracer" #37 😅 But yeah, I think the idea is to get rid of Fortran totally, and then I would give it a generic name. |
The references to fortran outside of the link to the class should at least be removed. This issue was also more general about just giving the docs a quick read through to make sure they are up to date. |
I guess the example gallery directory |
https://docs.sunpy.org/projects/sunkit-magex/en/latest/performance.html this still references "FORTRAN" in a few places.
The text was updated successfully, but these errors were encountered: