Difference between revisions of "IXTdata source"

From LIBISIS
Jump to navigation Jump to search
 
Line 5: Line 5:
 
The elements of the object are as follows:
 
The elements of the object are as follows:
  
<?plugin OldStyleTable caption="IXTdata_source" border||=2
+
{| border ="1" cellpadding="2"
|<  *Element|^ *Type* |^ *Brief Description*
+
|+ '''IXTdata_source definition'''
|<   path (:)    |^ char (allocatable) |< file path to data file
+
!width="10%"|Element  
|<   datatype (:)  |^ char (allocatable) |< type of data being stored in file
+
!width="20%"|Type  
|<   counter  |^ int  |< the number of items stored in the object
+
!width="70%"|Brief Description
?>
+
|-
 +
|   path (:)    || char (allocatable) || file path to data file
 +
|-
 +
|   datatype (:)  || char (allocatable) || type of data being stored in file
 +
|-
 +
|   counter  || int  || the number of items stored in the object
 +
|}
  
  

Revision as of 16:36, 30 January 2008

_*IXTdata_source*_

The IXTdata_source object is designed to store the path of specific files (.txt .nvs .xml etc.) which can be used to populate any object in the data structure. Or even to store characteristics such as the type of instrument being populated (in this instance the path variable is irrelevant).

The elements of the object are as follows:

IXTdata_source definition
Element Type Brief Description
path (:) char (allocatable) file path to data file
datatype (:) char (allocatable) type of data being stored in file
counter int the number of items stored in the object



F90 syntax


use IXMdata_source

type(IXTdata_source):: dso
type(IXTstatus):: status

The following operations may be performed on this data type:

  • [General Operations]
  • [Special Subroutines]

Class Specific Operations

  • [IXFadditem_data_source]
  • [IXFdelitem_dat_source]
  • [IXFfindpath_data_source]