Ticket #819 (closed Task: fixed)
simulation duration length should be an integer?
| Reported by: | rupert | Owned by: | gerry |
|---|---|---|---|
| Priority: | blocker | Milestone: | V1.1 Questionnaire Release |
| Component: | WP6 - CMIP5 Questionnaire | Version: | |
| Keywords: | subCMIP5 | Cc: | gerry, charlotte |
| Requirement: | http://metaforclimate.eu/Work-Package-2/Developing-the-CIM/Project-Requirements-summary.htm | ||
Description
Should the simulation duration length be an integer rather than a real number? Does it makes sense to have 0.123 years instead of a number of days? Actually should we instead have a date offset (does Django support such a thing?)?
Change History
comment:1 Changed 20 months ago by charlotte
- Milestone changed from V1.0 CMIP5 Questionnaire Release to V1.1 Questionnaire Release
comment:2 Changed 20 months ago by bryan
(so note that I don't think it's a blocker on V1.0 so I've bumped it.)
comment:3 Changed 20 months ago by rupert
The CIM now uses the schema duration type ( http://www.w3schools.com/Schema/schema_dtypes_date.asp) to store the duration information which makes it more important to turn this into an integer, or duration, in the questionnaire. At the moment I truncate the float to turn it into an int so it can be used to create the CIM duration type.
comment:4 Changed 20 months ago by gerry
- Owner changed from bryan to gerry
- Status changed from new to assigned
comment:6 Changed 15 months ago by gerry
- Status changed from assigned to closed
- Resolution set to fixed
I've now made it that the questionnaire checks that the simulation duration is entered as an integer, bouncing an error message back to the user if a float was entered. This was changed at the TimeLengthField? level which means any cases using this field class will be restricted to integers. I think this is what we want though.
