TRANSFER Import Definitions

<< Click to Display Table of Contents >>

Navigation:  Problem Descriptor Reference > The Sections of a Descriptor > Definitions >

TRANSFER Import Definitions

Previous pageReturn to chapter overviewNext page

FlexPDE supports a TRANSFER facility for exchanging data between FlexPDE problem runs.  The format is unique to FlexPDE, and is not supported by other software products.  The file format for version 7 is different from that of previous versions, but files written by version 6 can also be read by version 7.  See TRANSFER file format and TRANSFER6 file format for descriptions of the file formats.

A TRANSFER file contains data defined on the same unstructured triangle or tetrahedral mesh as used in the creating FlexPDE computation, and maintains the full information content of the original computation.  It also contains a description of the problem domain definition of the creating run.

Note: Unlike FlexPDE Version 6, Version 7 TRANSFER import restores the state of HISTORY plots (if the file was written by Version 7).


The TRANSFER input statement has three forms :

TRANSFER ( 'filename' , name1  { , name2 , ... } )
TRANSFERMESH ( 'filename', name1 { ,name2,.. } )

TRANSFERMESHTIME ( 'filename', name1 { ,name2,.. } )


The file specified in the transfer input function must have been written by FlexPDE using the TRANSFER output function.  The names listed in the input function will become defined as if they had appeared in a "name="  definition statement.  The names will be positionally correlated with the data fields in the referenced output file.

With the TRANSFER form, the mesh structure of the imported file is stored independently from the computation mesh, and is not influenced by refinement or merging of the computation mesh.  


The TRANSFERMESH input statement not only imports data definitions stored on disk, but also IMPOSES THE FINITE ELEMENT MESH STRUCTURE of the imported file onto the current problem, bypassing the normal mesh generation process. In order for this imposition to work, the importing descriptor file must have EXACTLY the same domain definition structure as the exporting file.  Be sure to use a copy of the exporting domain definition in your importing descriptor.  You may change the boundary conditions, but not the boundary positions and ordering.


The TRANSFERMESHTIME statement acts precisely as the TRANSFERMESH statement, except that the problem time is imported from the transfer file as well as the mesh.  This statement can be used to resume a time-dependent problem from the state recorded in the transfer file. In version 7 the TRANSFERMESHTIME statement is depricated and has been replaced by the RESTART statement.

Restart :


The RESTART input statement has the form :

RESTART ( 'filename' )


The file specified in the transfer input function must have been written by FlexPDE using the RESTART output function or the automatic .



Samples | Usage | Import-Export | Transfer_Export.pde

Samples | Usage | Import-Export | Transfer_Import.pde

Samples | Usage | Import-Export | Mesh_Export.pde

Samples | Usage | Import-Export | Mesh_Import.pde

Samples | Usage | Stop+Restart | Restart_Export.pde

Samples | Usage | Stop+Restart | Restart_Import.pde