Conversation
|
Open tasks
|
|
@dbarrous how do you want to proceed with this PR? |
@ehsteve I'm currently trying to abstract it a bit more so that we just have a singular For the open tasks on the levels, I'm going to import them from the mission package since that makes the most sense, and that way it isn't hard-coded into the processing module. Also still trying to figure out how to import hermes.log programmatically as well. |
|
I like the idea of hosting the variables in another file but seems like it would more appropriate as a non python file. Maybe a simple csv or a toml or yaml file? |
|
Great idea! ^ I'll put them in a YAML file, and pull from there. |
… that parses the yaml and can include any future helper functions. Fix dynamic import of instrument packages. Fix data_levels being hardcoded
… that parses the yaml and can include any future helper functions. Fix dynamic import of instrument packages. Fix data_levels being hardcoded
The purpose of this merge request is to abstract out our instrument and mission names so that other missions could use this. I also was able to optimize some of the code.
This is a work in progress.