Opened 7 years ago

Closed 3 years ago

#43 closed enhancement (wontfix)

Having the possibility of enforcing the addition of a axis to a file

Reported by: millour Owned by: ymipsl
Priority: minor Component: XIOS
Version: 2.0 Keywords:
Cc:

Description

So far if multiple axes are defined (e.g. axis1, axis2, etc.), but only one is used (e.g.all output fields in file are with axis_ref="axis2"), then it is the only axis written to the file.

Allowing users to specify that alternative axes, although not used, should be included in the output file would be useful.

Maybe by adding a flag output="always" to the axis (or file?) parameters?

Change History (5)

comment:1 in reply to: ↑ description ; follow-up: Changed 7 years ago by ymipsl

Replying to millour:

So far if multiple axes are defined (e.g. axis1, axis2, etc.), but only one is used (e.g.all output fields in file are with axis_ref="axis2"), then it is the only axis written to the file.

Yes, correct.

Allowing users to specify that alternative axes, although not used, should be included in the output file would be useful.

Why ? Do you have a good reason for this because it will take a lot of new development ?
In fact the connection between file and axis (or domain) is done through the field. A file doesn't know anything about axis that must be wrote only if it is referred by a field.

Maybe by adding a flag output="always" to the axis (or file?) parameters?

In fact, I think that the best way will be to embed axis (or domain or grid) inside a file by the same way as a field.

Yann

comment:2 in reply to: ↑ 1 ; follow-up: Changed 7 years ago by millour

Replying to ymipsl:

Replying to millour:

So far if multiple axes are defined (e.g. axis1, axis2, etc.), but only one is used (e.g.all output fields in file are with axis_ref="axis2"), then it is the only axis written to the file.

Yes, correct.

Allowing users to specify that alternative axes, although not used, should be included in the output file would be useful.

Why ? Do you have a good reason for this because it will take a lot of new development ?

It is mainly for postprocessing. For instance you declare vertical axes in pressure and altitude, and then switch from one to the other when visualizing the data (assuming the visualisation or post-processing software can do that).

In fact the connection between file and axis (or domain) is done through the field. A file doesn't know anything about axis that must be wrote only if it is referred by a field.

Maybe by adding a flag output="always" to the axis (or file?) parameters?

In fact, I think that the best way will be to embed axis (or domain or grid) inside a file by the same way as a field.

Yes indeed, this is probably the best way to handle it.

Ehouarn

comment:3 in reply to: ↑ 2 Changed 7 years ago by ymipsl

  • Priority changed from major to minor

Ok, so it will be available in the next branch XIOS_V2, planed in some month (probably September 2014).

Yann

comment:4 Changed 6 years ago by ymipsl

  • Version changed from 1.0 to 2.0

comment:5 Changed 3 years ago by ymipsl

  • Resolution set to wontfix
  • Status changed from new to closed

I close the ticket because it is very old.
We don't see a simple way to implement this functionality.
Nevertheless, if there is strong (and justified) request the ticket could be reopened.

Note: See TracTickets for help on using tickets.