Ticket #533 (new Task)

Opened 2 years ago

Last modified 20 months ago

EnsembleInputMods: What info is required in the Inputs Box?

Reported by: charlotte Owned by: charlotte
Priority: major Milestone: V1.2 Questionnaire release
Component: WP6 - CMIP5 Questionnaire Version: beta
Keywords: beta testing Cc: mariepierre, allyn
Requirement:

Description (last modified by bryan) (diff)

Testers: CERFACS (Marie Pierre)
Type: unclear (meaning)
Location: Simulation: Ensemble Characteristics Page: Input Modifications Page: Inputs Box

Is this box designed to select the "Reference Input" to which perturbation ("Input Modifications" are performed form an ensemble member to another? If so, an explanatory phrase would be welcome.

See more issues in ticket/684?

Change History

comment:1 Changed 2 years ago by charlotte

  • Cc mariepierre added; marie pierre removed

I am also not sure what is required here. Need to discuss with Bryan. I can then add explanatory text.

comment:2 Changed 2 years ago by bryan

  • Status changed from new to assigned

comment:3 Changed 2 years ago by charlotte

Bryan is reworking the format ot the model modification pages. I'll review this ticket after the beta2 release.

comment:4 Changed 2 years ago by bryan

  • Priority changed from major to blocker

Subsume ticket: 565 into this one. Ensure formatting on creation page and conformance page is ok with revisions:

the standard idea is that we have an input and a resolved input associated with the simulation, but the ensembles will have some different resolved inputs. I suspect this needs rethinking so that the input mods point to a new resolved input rather than the original input ... so in fact, an input mod is a coupling variation ... hmmm.

comment:5 Changed 2 years ago by allyn

  • Cc allyn added

This is related to issues concerning how the CIM will address ensembles.  There are two options under consideration:

1) By adding an optional ChangeProperty to the reference stereotype, an ensemble can contain multiple references to the same simulation and specify what about each simulation has changed.

2) We could also create a new class, EnsembleMember, which includes a reference to a base simulation and then a set of changes that is applied to make the member unique.  

Also in the CIM there is a place for ensembleType, but no content there.  I need to know what term to include in this enumeration.  I also need to know if this is the same as modificationType - if it isn't then that needs to be added somewhere (it would fit neatly into the EnsembleMember class proposed above).

comment:6 Changed 2 years ago by allyn

After further discussion, I am going with option 1 above.  I have added a changeType to a change which includes 'modelMod' and 'inputMod.'  This should be sufficient for CMIP5.

I still need an enumerated list for EnsembleTypes (which I've discovered is different than modification type).

comment:7 Changed 23 months ago by bryan

  • Description modified (diff)

comment:8 Changed 20 months ago by bryan

  • Owner changed from bryan to charlotte
  • Priority changed from blocker to major
  • Status changed from assigned to new

This is completely new now. Explanatory phrases probably needed. But not by me.

Note: See TracTickets for help on using tickets.