Creating EVS Presentations

The development of EVS Presentations (EVSP) from EVS Applications will nearly always require modification to your EVS application.  The key steps are:

1. Save your application.

2. Replace Disallowed Modules with acceptable replacements, if applicable.

   • Note: Not all Disallowed Modules have replacements which can be included in EVS Presentations.

3. Package all data files referenced in any modules. 

   • There cannot be any externally referenced data files.

   • Some modules cannot be packaged and are automatically replaced by the packaging process.  These include:

     1. import vector gis

     2. import cad

     3. import wavefront obj

   • Best if you don’t do this step sooner.

4. Add all desired module properties to Application Properties, so they can be accessed once the application is saved as an EVS Presentation. 

5. Backup your application as an EVS application to serve as an editable backup.

   • This is essential, should you wish to add additional module properties later.

6. Convert the application to an EVS Presentation (.evsp file).  

   • This is not a reversible process, which is why you want the backup from step 5.

 

What is Packaged Data

• Applications with packaged data include the data with the .EVS file.
• Packaged data:
  • Is data files that have been incorporated into your application
  • Can be most EVS files types
  • Must be done for all modules, if you plan to create an EVS Presentation
• Packaging of data can be done on a module-by-module basis, or for your entire application in one step.
• Applications with packaged data include the data with the .EVS file.

 

How to Package your data:

Module-by-Module method:

Right click on the filename in each module that read data (be sure you first remove all Disallowed Modules)

You will then see this message:

Select - "Convert to Packaged" and you should see the selected Filename change to Bold Blue text and also appear in the Packaged Files window.

Packaging All Files in One Step:

Please note that in the image above, we also see the "Package All Files in Application" button.

This button will find all of the files in your application and will package each one. After pressing this button, for this application we can see that there are only two modules which read files and their files are both packaged. Also note that if you can't find the "Packaged Files" window, make sure it is on (selected) in the Windows section of the Home tab.

NOTE: EVS will package the files for modules that are Disallowed for EVS Presentations. Just because a module's files will package is not a guarantee that it is allowed in an EVS Presentation.

Disallowed Modules and Replacements:

The following table lists all disallowed modules and their replacements if there are any.  Some modules, primarily interactive modules (e.g. modify_data_3d and create stratigraphic hierarchy) and export modules (e.g. export cad and export vector gis). 

Disallowed Module	Category	Replacement
external_kriging	Estimation	read evs field
2d estimation	Estimation	read evs field
3d estimation	Estimation	read evs field
scat_to_tri	Estimation	read evs field
scat_to_unif	Estimation	read evs field
modify_data_3d	Estimation/editing	none
combine horizons	Geologic modeling	read evs field
edit_horizons	Geologic modeling	read evs field
horizon_ranking	Geologic modeling	read evs field
lithologic modeling	Geologic modeling	read evs field
gridding and horizons	Geologic modeling	read evs field
create stratigraphic hierarchy	Geologic modeling	none
material_mapping	Geologic modeling	read evs field
drill_path	Geometry	none
analytical_realization	Geostatistics	read evs field
lithologic realization	Geostatistics	read evs field
stratigraphic_realization	Geostatistics	read evs field
well_decommission	Geostatistics	none
read_geometry	Import	read evs field
export horizon to raster	Export	none
export horizons to vistas	Export	none
export georeferenced image	Export	none
write_evs_field	Export	none
export web scene	Export	none
export pdf scene	Export	none
export 3d scene	Export	none
export vector gis	Export	none
export cad	Export	none
export nodes	Export	none
write_lines	Export	none
cell_computation	Python (Enterprise License Only)	read evs field (for Floating Licenses)
node_computation	Python (Enterprise License Only)	read evs field (for Floating Licenses)
trigger_script	Python (Enterprise License Only)	none (for Floating Licenses)

 

Restricted Functions:

In addition to the disallowed modules, certain integrated functions are restricted such as:

• Writing VRML files (for 3D PDFs)

• Recording 4DIMs

• Animator

  • Creating 4DIMs

  • Creation of bitmap animations (e.g. .AVI files)

• Tools Tab: All functions

• Open Python Script

  • Enterprise License customers may package Python scripts using the trigger_script module

EVSP Outputs:

The EVSP itself is intended to be the primary output, therefore the ability to create any outputs while and end-user works with an EVSP is limited to bitmap images. End-users will not be able to write any 3D type outputs (4DIM, VRML, Shapefiles, CAD files, etc.).