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

Five steps #1046

Open
edan-bainglass opened this issue Dec 31, 2024 · 2 comments
Open

Five steps #1046

edan-bainglass opened this issue Dec 31, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@edan-bainglass
Copy link
Member

edan-bainglass commented Dec 31, 2024

Step 3 always seemed like it was doing too much, both setting the resources AND submitting the job. I propose we split it in two, with step 3 setting the resources (it gets its own confirm button), and step 4 submitting the job, optionally setting the label and description.

image

So basically:

  1. Choose a structure
  2. Configure the calculation parameters
  3. Select the resources
  4. Submit the workflow
  5. Monitor and view results

@giovannipizzi @cpignedoli thoughts?

@edan-bainglass edan-bainglass added the enhancement New feature or request label Dec 31, 2024
@cpignedoli
Copy link
Member

One could then think it's too many steps but given I consider extremely important to focus on providing meaningful labels and descriptions I personally welcome your suggestion @edan-bainglass.

@giovannipizzi
Copy link
Member

I agree on splitting, it allows also, in the last step, to

  1. Show a summary of the selection, for confirmation (essentially, the same as the workflow summary that would be shown after submitting, if it's easy to do so?)

  2. In addition to label and description, one could set other metadata (e.g. add some extras/tags/keywords, or more importantly pick some groups to which the workflow should be added, as soon as submitted; in general, suggesting what we think people should do, and then using these as filtering strategies in the job list)

  3. Also here show again a summary of possible warnings (too few resources, etc, nothing new, only those already implemented)

  4. In the future one could have here some estimate of the expected wall time or cost, for instance

Note: the points above can be moved to a later, Lower priority issue, after the simple separation with only label/description setting)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants