Opened 11 years ago
Closed 8 years ago
#171 closed enhancement (fixed)
Proposition : change name for clean_month and clean_year
Reported by: | jgipsl | Owned by: | sdipsl |
---|---|---|---|
Priority: | minor | Milestone: | libIGCM_v2.8.2 |
Component: | treatment | Version: | |
Keywords: | Cc: |
Description
Proposition : Change name for clean_month.job into clean_PeriodLenght.job and change clean_year.job into clean_latestPackperiod.job. Or something similaire.
Also the comments in the beginning of these scripts are not correct : in clean_month, it says the script will clean a month.
Change History (8)
comment:1 Changed 11 years ago by sdipsl
- Milestone set to libIGCM_v2.2 metrics
comment:2 Changed 9 years ago by sdipsl
- Owner changed from somebody to sdipsl
- Status changed from new to assigned
comment:3 Changed 9 years ago by sdipsl
- Milestone set to libIGCM_v2.8
comment:4 Changed 9 years ago by mafoipsl
In the current version, Analyse/SE files are not included in the cleaning.
Don't forget to delete dods file also.
comment:5 Changed 9 years ago by sdipsl
Generally speaking nothing from the post processing has never been included in the cleaning Analyse/SE and Analyse/TS_*, Monitoring ...
Why should we include it now? If rebuild or pack_output failed create_* wont be launched. And if they are it is a mistake
.
comment:6 Changed 8 years ago by sdipsl
- Milestone libIGCM_v2.8 deleted
comment:7 Changed 8 years ago by sdipsl
- Milestone set to libIGCM_v2.9
will do that for the next release. We will follow the same strategy we followed for ins_job. clean_* will echo a message stating one need to use renamed scripts.
comment:8 Changed 8 years ago by sdipsl
- Resolution set to fixed
- Status changed from assigned to closed
I agree on this. If no one object I will do it.