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

Make sim configuration templates more accessible #1639

Open
bradNASA opened this issue Mar 7, 2025 · 0 comments
Open

Make sim configuration templates more accessible #1639

bradNASA opened this issue Mar 7, 2025 · 0 comments
Labels
feature New feature or request soon srl Requests from the SRL project

Comments

@bradNASA
Copy link

bradNASA commented Mar 7, 2025

Checked for duplicates

Yes - I've already checked

Alternatives considered

Yes - and alternatives don't suffice

Related problems

I'm frustrated when I make a small change to a mission model, and the simulation configuration templates I created for previous versions don't apply even though the sim configuration parameters haven't changed at all.

I could use aerie-cli or hasura to download and upload templates, but that's often more painful than re-creating the templates manually (which can be error prone).

Describe the feature request

I want my templates to be there when I add a new mission model, and even if I change the sim configuration, there's a common sense way to automatically migrate them to fit as best as possible. If the parameters are different from the last mission model (or all mission models), there could be some threshold of mismatches where the user is asked to specify whether or not to migrate some smartly selected set of templates.
But, as long as it is smart, maybe bugging the user is unnecessary because you can make all of them accessible, as discussed below.

There could be a problem where the server has many templates from many users, so including all of those in a dropdown for every user and every mission model could be problematic. Maybe a pattern for how other things are shared can be used (like for sharing scheduling goals). Forgetting how those are done, I could imagine that templates could be grouped by

    • those applied to the current mission model,
    • those for other mission models,
    • for the current user, and
    • for all users.

So, when a user selects the template drop-down, they see those from group 1, and they can open up other groups somehow.

There are many ways this might be done. Feedback from this feature's requestors, Maggie Mende or Brad Clement, will be happily given.

@bradNASA bradNASA added feature New feature or request srl Requests from the SRL project labels Mar 7, 2025
@joswig joswig added the soon label Mar 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request soon srl Requests from the SRL project
Projects
None yet
Development

No branches or pull requests

2 participants