Custom Query (116 matches)
Results (34 - 36 of 116)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#87 | worksforme | Duration arithmetics does not work | ymipsl | ssenesi |
Description |
According to the ref_guide : Arithmetic operations on durations The following arithmetic operations on durations are available: • Addition: xios_duration = xios_duration + xios_duration • Subtraction: xios_duration = xios_duration - xios_duration • Multiplication by a scalar value: xios_duration = scalar * xios_duration or xios_duration = xios_duration * scalar • Negation: xios_duration = -xios_duration But gfortran doesn't agree : CALL XIOS_SET_FIELD_ATTR(HREC, freq_op=KFREQOP*XIOS_HOUR)
Error: Operands of binary numeric operator '*' at (1) are INTEGER(4)/TYPE(xios_duration) CALL XIOS_SET_FIELD_ATTR(HREC, freq_offset=0.*XIOS_SECOND)
Error: Operands of binary numeric operator '*' at (1) are REAL(8)/TYPE(xios_duration) |
|||
#89 | invalid | Error in node/domain.cpp on ChecKDomainData | ymipsl | ssenesi |
Description |
It reads on line 792 as if (data_ni.isEmpty()) { data_ni.setValue((data_dim == 1) ? (ni.getValue() * nj.getValue()) : ni.getValue()); } which is obviously wrong (set values should be reversed). This actually causes segmentation violation when nj is not set and data_dim==1; and this should lead to underestimated allocation when data_dim==2 |
|||
#62 | fixed | Feeding a 2D global grid with processes working 1D is not working | ymipsl | ssenesi |
Description |
Attached source test1d.90 is a modified version of test_complete.f90. It reduces nj_glo to a value of 3 (instead of 100°. Next, it defines "domain_1" as being the same global domain as "domain_A", being fed by processes which work on the same 2D sub-domains as for domain_A, except that they declare themselves to Xios as being 1D sub-domains, and they provide i_index and j_index for describing the mapping of the 1D local data to the 2D global domain. Execution results in incorrect data in field_1 (which actually receive, at some location, values from field_A at llm=3) . This may be due to misunderstanding in the API arguments in this configuration iodef.xml and result file are also attached |