You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Generating event-specific MTUQ scripts in this way can help avoid some tedious copying and pasting. Also, could be helpful as UAF seeks a reproducible, standardized workflow?
The text was updated successfully, but these errors were encountered:
Hi @rmodrak, this looks like a great idea. Let me know if you need anything on the PySEP end.
One thing I'll note is that since the scope of PySEP has broadened, the current, default PySEP settings do not create the requisite MTUQ files, so a user would have to know which flags to turn on to get the required weights files, and output with a file naming format that MTUQ can parse.
Perhaps adding a flag, e.g., pysep ./config.yaml --mtuq_ready (or similar naming) could help standardize things for MTUQ input, and would be useful for MTUQ users?
An approach for generating event-specific MTUQ scripts from PySEP config files:
https://github.com/rmodrak/mtuq_script_generator/blob/3e2181639da4615822e5610c077a06d19827288c/mtuq_script_generator.py#L110
Generating event-specific MTUQ scripts in this way can help avoid some tedious copying and pasting. Also, could be helpful as UAF seeks a reproducible, standardized workflow?
The text was updated successfully, but these errors were encountered: