Opened 4 years ago

Closed 3 years ago

#121 closed defect (fixed)

mess in time axes

Reported by: ssenesi Owned by: ymipsl
Priority: major Component: XIOS
Version: 2.0 Keywords:


Using a toy client like test_grid (see former ticket), and

  • defining one field with operation=instant, freq_op=2ts
  • requesting it with output_freq=1ts,
  • running for 4 timesteps with a 600s timestep

I get an output with coordinates="... time_instant" and a time_instant variable which has values : [ 600, 1200, -, -]

This seems odd; I was expecting either :

1- a time_instant variable with values [ 600, 1200, 1800, 24000 ] and fields filled with missing values for instants 600 and 1800
2- or a time_instant variable with values [ 1200, 2400, - , - ]

The same occurs if, instead of setting freq_op=2ts, I send the field only one out of 2 timesteps

What did I miss ?

Change History (2)

comment:1 Changed 4 years ago by ymipsl


freq_op is generaly used to make sub-sampling for temporal operator. That means you make your temporal integration taking a incoming flux every freq_op. To be coherent with output frequency, it must an exact divisor of output_freq. In your case, you want to output every timestep but taking a instant value every 2 timestep. It is not coherent with your output frequency, the result is undefined.

This is actually the rules. In the future, we will work to improve the integration of temporal flux, an these rules will be more flexible.



comment:2 Changed 3 years ago by ymipsl

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.