Output from the PT simulations

The result files will be located in standard Results directory for your project. The PT result files are:

·         projectname.PTRES: An ASCII file in pfs-format listing the abstraction wells and the computational cells, where abstraction occurs. Used for retrieval of particle location - see PT Registration Extraction (V1 p. 372).

·         projectname.PTREG and projectname.trf: Two binary files that cannot be opened directly.

·         projectname.PTBIN: An optional binary file containing all of the particle locations at every saved time step. Individual path lines can be extracted using the Extraction of Particle Path Lines (V1 p. 731).

·         projectname.PTGross.shp: An optional point theme shape file contain­ing the path line information of every particle at every saved time step. As part of the shape file, a .shx and a .dbf file are also created. The .dbf file can be opened in Excel if it is less than 65536 lines.

·         projectname_AD_3DSZ.dfs3: Temporal and spatially varying SZ con­centrations in the mobile phase based on the mass of the particles.

·         projectname_PT_3DSZ.dfs3: Temporal and spatially varying PT results including:

         Number of particles - this is the actual number of particles in each cell

         Accumulated particle count – this is the number of particles that have entered the cell during the simulation

         Number of registered particles – this is the number of particles that started in this cell that have become registered

         Most recent registration zone – this is the registration zone attached to the last particle to be registered that originated in the cell

         Average age – this is the average age of all the particles in the cell

         Average transport time – this is the average length of time from when the particle was born in this cell until it was registered some­where

Besides these result files, the program also writes output to two log files. The error log list errors encountered during execution and the print log file con­tains execution step information, statistics on the run and a mass balance (if requested).