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

including tracefunction in stored comps #13

Open
tcrundall opened this issue May 18, 2021 · 1 comment
Open

including tracefunction in stored comps #13

tcrundall opened this issue May 18, 2021 · 1 comment
Assignees

Comments

@tcrundall
Copy link
Collaborator

With the introduction of multiple (i.e. 2) different orbit tracing functions with slightly different results, it is maybe important to store with a component which function was used to fit it.

@tcrundall
Copy link
Collaborator Author

For including the tracing method into the raw stored components this might be tricky encoding that information into an array.

Maybe the components should start being stored as fits files by default, and that way the trace function can be included in as a string. For backwards compatibility when loading a component from a file it can first try the fits file, then if it’s missing do the numpy file and assume (probably) the epicyclic function.

@tcrundall tcrundall assigned tcrundall and marusazerjal and unassigned tcrundall May 18, 2021
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