Custom Query (116 matches)
Results (34 - 36 of 116)
Ticket
|
Resolution
|
Summary
|
Owner
|
Reporter
|
#58 |
fixed
|
wrong result for "xios_is_valid_context" call
|
rlacroix
|
ymipsl
|
Description |
From Mike Rezny :
The following program does not give the result I was expecting:
PROGRAM test1
USE xios
USE mod_wait
USE mpi
IMPLICIT NONE
- CHARACTER(len=*),PARAMETER
- id = "client"
- CHARACTER(len=128)
- value
- TYPE(xios_time)
- dtime
- TYPE(xios_context)
- ctx_hdl
- TYPE(xios_domain)
- domain_hdl
- TYPE(xios_axis)
- axis_hdl
- TYPE(xios_grid)
- grid_hdl
- TYPE(xios_fieldgroup)
- fieldgroup_hdl
- TYPE(xios_field)
- field_hdl
- TYPE(xios_file)
- file_hdl
- INTEGER
- comm, rank, size, ierr
- LOGICAL
- ok
CALL MPI_INIT(ierr)
CALL init_wait
CALL xios_initialize(id, return_comm = comm)
CALL MPI_COMM_RANK(comm, rank, ierr)
CALL MPI_COMM_SIZE(comm, size, ierr)
CALL xios_context_initialize("test", comm)
CALL xios_get_handle("test", ctx_hdl)
CALL xios_set_current_context(ctx_hdl)
CALL xios_get_handle("domain_A", domain_hdl)
CALL xios_get_handle("axis_A", axis_hdl)
CALL xios_get_handle("grid_A", grid_hdl)
PRINT *, 'valid context [test]: ', xios_is_valid_context("test")
PRINT *, 'valid domain [domain_A]: ', xios_is_valid_domain("domain_A")
PRINT *, 'valid axis [axis_A]: ', xios_is_valid_axis("axis_A")
PRINT *, 'valid grid [grid_A]: ', xios_is_valid_grid("grid_A")
CALL xios_close_context_definition()
CALL xios_context_finalize()
CALL xios_finalize()
CALL MPI_FINALIZE(ierr)
END PROGRAM test1
The program output is:
valid context [test]: F
valid domain [domain_A]: T
valid axis [axis_A]: T
valid grid [grid_A]: T
Why is the program returning FALSE for the context ‘test’? I was expecting TRUE.
I am sure that I do not understand something.
Here is the XML input file:
<?xml version="1.0"?>
<simulation>
<context id="test" calendar_type="Gregorian" start_date="2012-03-01 15:00:00" >
<domain_definition>
<domain id="domain_A" />
</domain_definition>
<axis_definition>
<axis id="axis_A" />
</axis_definition>
<grid_definition>
<grid id = "grid_A" />
</grid_definition>
<field_definition level="1" enabled=".FALSE." >
<field id="field_A" operation="average" freq_op="3600s"
grid_ref="grid_A" />
</field_definition>
<file_definition
type = "multiple_file"
par_access = "collective"
output_freq = "6h"
output_level = "10"
enabled = ".TRUE." >
<file id="output" name="output" >
<field field_ref="field_A" />
</file>
</file_definition>
</context>
<context id="xios">
<variable_definition>
<variable_group id="buffer">
buffer_size = 8000000
buffer_server_factor_size = 2
</variable_group>
<variable_group id="parameters" >
<variable id="using_server" type="boolean" >
false
</variable>
<variable id="info_level" type="int" >
50
</variable>
</variable_group>
</variable_definition>
</context>
</simulation>
kindest regards
Mike
|
#59 |
fixed
|
Floating Point Exception when output_frequency < timestep
|
oabramkina
|
ssenesi
|
Description |
If a an output_freq of "2h" is set, my model having a timestep of 3h, XIOS does crash with FPE. Increasing output_freq to 3h 'solves' the problem. A smoother , landing with an an explicit explanantion would be friendlier.
|
#60 |
fixed
|
String variable with whitespaces are incorrectly parsed
|
rlacroix
|
rlacroix
|
Description |
How to reproduce:
<file_definition type="multiple_file" par_access="collective" output_freq="6h" output_level="10" enabled=".TRUE.">
<file id="output" name="output">
<field field_ref="field_A" />
<variable id="my_attribute1" type="string">surf_att</variable>
<variable id="my_attribute2" type="string">I love whitespaces</variable>
</file>
</file_definition>
Using this configuration file will result in the following NetCDF output:
// global attributes:
:name = "output" ;
:description = "Created by xios" ;
...
:my_attribute1 = "surf_att" ;
:my_attribute2 = "I" ;
Expected result would be :my_attribute2 = "I love whitespaces" ;
|
Note: See
TracQuery
for help on using queries.