Running BlobFlow$^{\rm TM}$

To run BlobFlow$^{\rm TM}$ after properly setting the environment variables, one merely executes the command:

eflow

BlobFlow$^{\rm TM}$ generates a number of output files. A computational log file, called $(ECCSVM_BASENAME)_comp.log, contains ordinary information about BlobFlow$^{\rm TM}$ as it progresses through the computation. If one is running BlobFlow$^{\rm TM}$ across multiple processors with MPI, each process generates a computational log with the name $(ECCSVM_BASENAME)_compn.log where n is the process rank beginning with 0. There is a diagnostic log file called $ECCSVM_BASENAME_diag.log for debugging purposes. Under ordinary circumstances, this file should remain empty. If one is running the code with a multiprocessor, message passing log files are generated with the file names $(ECCSVM_BASENAME)_mpin.log.

The vorticity field is written to files in the form $(ECCSVM_BASENAME)nnnn.vtx where nnnn a four digit index for the state being dumped. If the FrameStep parameter is set to 0.1, the file $(ECCSVM_BASENAME)1234.vtx contains basis functions representing the vorticity field at time t=123.4. Each line of the file contains six parameters describing a basis function as in the definition of VtxInit. If one is running across multiple processors, only the process of rank 0 will write data files.