Salome HOME
projects
/
modules
/
med.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
updated copyright message
[modules/med.git]
/
idl
/
MEDDataManager.idl
diff --git
a/idl/MEDDataManager.idl
b/idl/MEDDataManager.idl
index 6f46be875efd0a88ba36ad223f9ae1753abdf8e1..ef4068178b9bd00569802adff18960d5e4ba3c13 100644
(file)
--- a/
idl/MEDDataManager.idl
+++ b/
idl/MEDDataManager.idl
@@
-1,4
+1,4
@@
-// Copyright (C) 2007-202
0 CEA/DEN, EDF R&D
, OPEN CASCADE
+// Copyright (C) 2007-202
3 CEA, EDF
, OPEN CASCADE
//
// Copyright (C) 2003-2007 OPEN CASCADE, EADS/CCR, LIP6, CEA/DEN,
// CEDRAT, EDF R&D, LEG, PRINCIPIA R&D, BUREAU VERITAS
//
// Copyright (C) 2003-2007 OPEN CASCADE, EADS/CCR, LIP6, CEA/DEN,
// CEDRAT, EDF R&D, LEG, PRINCIPIA R&D, BUREAU VERITAS
@@
-45,17
+45,17
@@
module MEDCALC
typedef sequence<MeshHandler> MeshHandlerList;
/**
typedef sequence<MeshHandler> MeshHandlerList;
/**
- * The Fieldseries is a virtal object that does not exist in the MED
+ * The Fieldseries is a virt
u
al object that does not exist in the MED
* data model (at least in the MEDCoupling data model). It is just a
* data model (at least in the MEDCoupling data model). It is just a
- * point that aggregate
a list of fields that relie
on the same mesh
+ * point that aggregate
s a list of fields that rely
on the same mesh
* with the same type (the fields in a timeseries differ by their
* time step).
*
* Then you could have a field with no fieldseries associated but
* directly associated to a mesh. That is typically the case of
* with the same type (the fields in a timeseries differ by their
* time step).
*
* Then you could have a field with no fieldseries associated but
* directly associated to a mesh. That is typically the case of
- * fields created by MED operations: if you operate t
ow
fields
+ * fields created by MED operations: if you operate t
wo
fields
* coming from 2 different timeseries (and relying on the same
* coming from 2 different timeseries (and relying on the same
- * mesh), you obtain a field that can not be associate to the
+ * mesh), you obtain a field that can not be associate
d
to the
* original timeseries. Then this new created field must be directly
* associated to its underlying mesh (as defined in the MEDCoupling
* data model).
* original timeseries. Then this new created field must be directly
* associated to its underlying mesh (as defined in the MEDCoupling
* data model).
@@
-133,6
+133,8
@@
module MEDCALC
FieldseriesHandlerList getFieldseriesListOnMesh(in long meshId);
FieldHandlerList getFieldListInFieldseries(in long fieldseriesId);
FieldseriesHandlerList getFieldseriesListOnMesh(in long meshId);
FieldHandlerList getFieldListInFieldseries(in long fieldseriesId);
+ long getFieldIdAtTimestamp(in long fieldseriesId, in double timestamp);
+
FieldHandler getFieldHandler(in long fieldHandlerId);
FieldHandlerList getFieldHandlerList();
// __GBO__ Maybe it could be useful to define a getFieldHandlerList with a datasourceId in argument
FieldHandler getFieldHandler(in long fieldHandlerId);
FieldHandlerList getFieldHandlerList();
// __GBO__ Maybe it could be useful to define a getFieldHandlerList with a datasourceId in argument
@@
-154,6
+156,8
@@
module MEDCALC
//void saveFields(in FieldHandlerList fieldHandlerList, in string filepath);
//void saveFields(in FieldHandlerList fieldHandlerList, in string filepath);
+ double getFieldTimestamp(in long fieldHandlerId);
+
void changeUnderlyingMesh(in long fieldHandlerId, in long meshHandlerId)
raises (SALOME::SALOME_Exception);
void changeUnderlyingMesh(in long fieldHandlerId, in long meshHandlerId)
raises (SALOME::SALOME_Exception);