Custom Query (116 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (103 - 105 of 116)

Ticket Resolution Summary Owner Reporter
#33 fixed bugfix in attribute_array_impl.hpp? ymipsl smasson
Description

Should the following bugfix be commited?

-bash-4.1$ svn diff
Index: src/attribute_array_impl.hpp
===================================================================
--- src/attribute_array_impl.hpp        (revision 446)
+++ src/attribute_array_impl.hpp        (working copy)
@@ -75,8 +75,12 @@
     template <typename T_numtype, int N_rank>
     void CAttributeArray<T_numtype,N_rank>::setInheritedValue(const CAttributeArray& attr)
     {
-      if (this->isEmpty() && attr.hasInheritedValue()) inheritedValue=attr ;
-     } 
+      if (this->isEmpty() && attr.hasInheritedValue()) 
+      {
+        inheritedValue.resize(attr.shape()) ;
+        inheritedValue=attr ;
+      }
+    } 
 
     template <typename T_numtype, int N_rank>
     CArray<T_numtype,N_rank> CAttributeArray<T_numtype,N_rank>::getInheritedValue(void) const

#48 fixed bibliographic citation for reference to xios ? ymipsl theetten
Description

Hello,

Is there a bibliographic citation for xios ? What reference should be given in article, poster, etc ?

Thanks, Sébastien

#95 fixed Alternate, sensible, convention for lonvalue_1d when data_dim=1, for a rectilinear domain ymipsl ssenesi
Description

In domain.cpp, for the case of a rectilinear domain, completeLonLatClient uses lonvalue_1D with an implicit assumption that the distribution also is recti-linear (i.e. that each MPI tasks does process a rectangle in the lat-lon space)

This does not apply when data_dim=1 and the distribution follows another scheme.

The attached version of domain.cpp, domain_new.cpp, is a proposal for an alternate convention in that case : lonvalue_1d and latvalue_1d are then interpreted as providing arrays which are parallel to the data arrays (which is more intuitive in that data_dim=1 case)

Note: See TracQuery for help on using queries.