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
{{ message }}
This repository has been archived by the owner on Oct 22, 2024. It is now read-only.
Creating the issue just so we don't forget about it.
@agayayav had a question in Slack about setting statuses of tasks using multiple date periods,
Hi! Some fast command to set 10 years in monthly chunks to completed?
We were trying this: autosubmit setstatus a06x -ftc "19(500101-591201), fc1, SIM" -t COMPLETED -s
But it was not working
And @mcastril replied with a solution, and also a suggestion for how to use the Web GUI to figure out the command (if I understood it correctly):
I had an idea regarding that question. The GUI is not yet deployed for the Climate DT. But in case that you need help with the setstatus, you can get a similar command for an experiment similar to yours and then only do a few modifications.
I ammend what I said. It's not really working because the GUI does not group tasks, it only uses the -fl filter. So we have a possible improvement for the GUI
The text was updated successfully, but these errors were encountered:
The idea is that the GUI setstatus hing functionality should be smart enough to check if all the tasks belong to the same startdate and member and it's shorter to use -fc filter.
The use of -ft or -fs is more risky as the workflow status may change and the command lead to a different effect that the one intended by the user.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In GitLab by @bdepaula on Jul 25, 2023, 18:05
Creating the issue just so we don't forget about it.
@agayayav had a question in Slack about setting statuses of tasks using multiple date periods,
And @mcastril replied with a solution, and also a suggestion for how to use the Web GUI to figure out the command (if I understood it correctly):
The text was updated successfully, but these errors were encountered: