GitLab

Commit patch from Pat Collins allowing light data limit to be set from
Fortran interface.

If xml is parsed from a string its document url could be NULL which causes
an error when building a map of document urls to documents.

Add method to output heavy data.
Add method to read file from disk.

Output of Xdmf data in Fortran can now take advantage of xpointer functionality.
Calling any AddPrevious or SetPrevious methods will reuse previously
added Xdmf structure so that when it is written to disk xincludes can be
utilized rather than rewriting identical structure multiple times.  These
methods take an id which is returned in Add or Set calls.

Modified TestXdmfFortran.f90 to utilize new functionality.

Eliminate getRealPath calls which are expensive and not necessary in many cases
Parse XML node content only when necessary (parsing arrays)
Fix cases where copies were made of strings instead of using references
Use "map.insert()" rather than "map[] =" when adding properties to map

Just input file into partitioner with new number of processes. The file
is unpartitioned in memory and repartitioned.

Use -u flag to unpartition a previously partitioned mesh.

Slightly improves compile time on gcc.
Get rid of mHaveArray and mHaveArrayPointer - rely on blank in variant.
This reduces code and makes logic easier to understand.

Choose dataset name more carefully to avoid querying the file many times.
Use a more efficient function to check if a dataset already exists in a file.
Get DSM working with new changes.
Fix gcc compiler warning in test.

Previously, each time a dataset was written to hdf5, the file was opened
and closed. This was implemented because inside the heavy data writer
we have no idea whether another dataset will be written, so we don't know
whether to keep the file open. After profiling large xdmf writes it was
determined that closing the file appeared to be a bottleneck so hooks were
added to the heavy data writer to open the file and keep it open while writing.
This is optional, but was incorporated into several higher level classes
like XdmfWriter where we know we can leave a file open until we finish writing
the XML. For our test problem we saw a 7 time performance gain.

when writing out file to disk.

fragment was surrounded by an <Xdmf> tag.

The bug appears when trying to use a filename given as:
file:///path/to/xmf/file.xmf and the xmf contains a reference to an h5 file.

- When writing you will end up with a file called 'file:' which contains
random data.
- When reading, libxml2 has no problem opening the xml file however
getRealPath() returns the wrong path for the h5 file. If you try to
use file.xmf from the to directory (ie: read("to/xmf/file.xmf")) the
h5 file will be loaded from 'to/file.h5'.

To correct the issue, we strip out the unwanted scheme and other stuff
in the URI and just use the path. (libxml has functions for this)

Additional xmf files are now read in via href'd xincludes which broke
mapping of xmlNodePtrs to XdmfItems (which qas necessary to enable shared
pointer representation in file).  This mapping was fixed.

XdmfCoreReader.cpp had a bug that resulted in an infinite loop when
resolving xincludes. This bug was fixed. Added ability for xincludes
to resolve href links (links to other files).

Fixed formatting in XdmfWriter.cpp

Unpartition method takes an XdmfGridCollection of unstructured grids
and zips them back together into a single XdmfUnstructuredGrid. It uses
GlobalNodeIds to perform the unpartitioning.

Also added some functionality to the partitioner so that it will properly
partition set attributes of types other than scalar.