Opened 15 years ago
Closed 13 years ago
#13 closed task (fixed)
Documenter la philosophie sous jacente aux monitoring et aux atlas
Reported by: | sdipsl | Owned by: | brocksce |
---|---|---|---|
Priority: | minor | Milestone: | libIGCM_v2.0 |
Component: | Documentation | Version: | |
Keywords: | Cc: |
Description
- Comment sont construits les noms de fichiers cfg pour le monitoringO1, comment faire pour intervenir dessus.
- Comment débuguer un monitoring01 quand rien se passe (la commande monitoring01 est lancé mais on ne voit pas de monitoring01)
- Idem pour les atlas, en détaillant la logique des atlas*cfg :
atlas_p_LMDZ_diag0_a.cfg, ..., atlas_p_LMDZ_diag1_ae.cfg, ...
Change History (6)
comment:1 Changed 15 years ago by sdipsl
- Priority changed from major to minor
comment:2 Changed 15 years ago by sdipsl
- Milestone changed from libIGCM_v1.3 to libIGCM_v1.5
comment:3 Changed 14 years ago by sdipsl
- Milestone changed from libIGCM_v1.5 to libIGCM_v1.6
comment:4 Changed 14 years ago by sdipsl
- Milestone changed from libIGCM_v1.6 to libIGCM_v1.7
comment:5 Changed 13 years ago by sdipsl
- Milestone changed from libIGCM_v1.7 to libIGCM_v2.0
comment:6 Changed 13 years ago by sdipsl
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
Fait dans le cours. Lien mis depuis la doc utilisateur libigcm
http://forge.ipsl.jussieu.fr/igcmg/attachment/wiki/IPSLCM5A/Cours-modipsl-dec2010.pdf