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
Currently CSET creates a webpage using a server specified (usually www-nwp/), but those outside the Met Office cannot view. There is also a risk that if a user cleans the suite, it will remove all the plots. So the question is there a way to 'export' a CSET webpage and plots into some modular format that we can share with partners via JASMIN, or archive/put in a better location for safekeeping? Particularly if we run CSET through a big trial and multiple people will refer to those CSET webpages in the future.
The text was updated successfully, but these errors were encountered:
Fundamentally CSET produces a set of static web files, saved in the workflow's shared directory, and symlinked to from the WEB_DIR (usually $HOME/public_html/CSET).
The WEB_ADDR configuration (which is the www-nwp URL inside the Met Office) is only used in the notification email sent at the end of the workflow run, so the output can be linked to directly. The only place it is used is in send_email.py.
If you want to archive or share the output it suffices to share the content of the WEB_DIR.
A separate consideration is whether we want to add easy publishing to something like JASMIN, where instead of being saved to a local WEB_DIR, it is deployed directly on JASMIN.
Currently CSET creates a webpage using a server specified (usually www-nwp/), but those outside the Met Office cannot view. There is also a risk that if a user cleans the suite, it will remove all the plots. So the question is there a way to 'export' a CSET webpage and plots into some modular format that we can share with partners via JASMIN, or archive/put in a better location for safekeeping? Particularly if we run CSET through a big trial and multiple people will refer to those CSET webpages in the future.
The text was updated successfully, but these errors were encountered: