Opened 14 months ago

Last modified 14 months ago

#706 new defect

interMonitoring

Reported by: mmcgrath Owned by: somebody
Priority: minor Milestone: Not scheduled yet
Component: Tools Version:
Keywords: Cc:

Description

This tool (http://webservices.ipsl.fr/interMonitoring/) is very nice for comparing completed timeseries across different runs that have been placed on the THREDDS server on Irene/Ciclad (for example, but running in the PROD directory in config.card).

Sometimes, the time series post-processing job does not finish (noticed for r6616, r6642, and others on Irene, global runs). Deleting all the MONITORING files (work/cont003/thredds/.../MONITORING/, work/cont003/gen6328/.../MONITORING) and relaunching the TimeSeries.job (https://forge.ipsl.jussieu.fr/igcmg_doc/wiki/Doc/CheckDebug#Startorrestartpostprocessingjobs) can make the completed files show up on the monitoring tool (https://vesg.ipsl.upmc.fr/thredds/catalog/work/USERNAME/catalog.html), but not on the interMonitoring tool.

The monitoring tool also have graphics produced for all files, so you can see simulation totals as a function of time. However, you cannot compare multiple runs, like you can on interMonitoring.

Change History (1)

comment:1 Changed 14 months ago by mmcgrath

Josefine and I discussed this a little with some input from Patrick. Patrick seems to feel that there is an unseen problem in the time axis of the monitoring files that is causing the interMonitoring tool to choke, based on trying to load the files in ferret. This error appears for both the files on the thredds server and the workdir MONITORING, but in one case 340 values appear and in the other, only 40 (for this particular file).

* NOTE: Valid calendars are GREGORIAN,NOLEAP,JULIAN,360_DAY,ALL_LEAP,PROLEPTIC_GREGORIAN
* NOTE: calendar attribute on axis "TIME_COUNTER" is not recognized: NONE
* NOTE: A dummy axis of subscripts will be used
* NOTE: Valid calendars are GREGORIAN,NOLEAP,JULIAN,360_DAY,ALL_LEAP,PROLEPTIC_GREGORIAN
* NOTE: Valid calendars are GREGORIAN,NOLEAP,JULIAN,360_DAY,ALL_LEAP,PROLEPTIC_GREGORIAN

None of us knows why.

Note: See TracTickets for help on using tickets.