HVIEW2D - Revision history

Ak3glang: working group POS

2022-09-06T09:43:14Z

working group POS

← Older revision		Revision as of 09:43, 6 September 2022
Line 3:		Line 3:
	\|name=HVIEW2D		\|name=HVIEW2D
	\|version=February 2016		\|version=February 2016
	\|version_descr=~~October 2015~~		\|version_descr=September 2022
	\|catchwords=graphical postprocessor<br />		\|catchwords=graphical postprocessor<br />
	finite element models<br />		finite element models<br />
Line 87:		Line 87:
	\|language=Fortran90		\|language=Fortran90
	\|add_software=GKS (by GTS-Gral)		\|add_software=GKS (by GTS-Gral)
	\|contact_original=~~[mailto:jens.juerges@baw.de~~ J. Jürges],~~[mailto:guenther.lang@baw.de~~ G. Lang],~~[mailto:ingrid.uliczka@baw.de~~ I. Uliczka]		\|contact_original=J. Jürges, G. Lang, I. Uliczka
	\|contact_maintenance=[mailto:~~jens~~.~~juerges~~@baw.de ~~J. Jürges],[mailto:guenther.lang@baw.de G. Lang], [mailto:susanne.spohr@baw.de S. Spohr~~]		\|contact_maintenance=[mailto:pos.proghome@baw.de Working group POS]
	\|documentation=Ion A. Angell und Gareth H. Griffith, 1989: Praktische Einführung in die Computer-Graphik mit zahlreichen Programmbeispielen, Hanser Verlag, 360 Seiten.		\|documentation=Ion A. Angell und Gareth H. Griffith, 1989: Praktische Einführung in die Computer-Graphik mit zahlreichen Programmbeispielen, Hanser Verlag, 360 Seiten.

imported>Spohr Susanne: Link to PARTRACE-3D removed.

2017-08-11T08:46:04Z

Link to PARTRACE-3D removed.

← Older revision		Revision as of 08:46, 11 August 2017
Line 83:		Line 83:
	In the course of the second processing step any polygon with assigned data may be optionally split at intersecting isolines into a series of smaller polygons. This kind of graphical data representation is much more expensive compared to the simplier shading of the original (unsplit) polygon but it is well suited to show more details of the data in areas with a small number of triangles.		In the course of the second processing step any polygon with assigned data may be optionally split at intersecting isolines into a series of smaller polygons. This kind of graphical data representation is much more expensive compared to the simplier shading of the original (unsplit) polygon but it is well suited to show more details of the data in areas with a small number of triangles.
	In the final processing stage all the data which have been assigned to the scene are converted into one of the several possible graphical representations (see also the examples given above).		In the final processing stage all the data which have been assigned to the scene are converted into one of the several possible graphical representations (see also the examples given above).
	\|preprocessor=[[DATACONVERT]], [[DIDAMERGE]], [[DIDAMINTZ]], [[DIDASPLIT]], [[ENERF]], [[FRQWF]], [[GRIDCONVERT]], [[LZKAF]], [[LZKMF]], [[LZKSF]], [[LZKVF]], [[LZKWF]], [[METDIDA]], [[PARTRACE~~]], [[PARTRACE-3D~~]], [[POLWIND]], [[PGCALC]], [[TELEMAC-2D]], [[TM2DIDA]], [[TR2APP]], [[TR2DIDA]], [[TR3DIDA]], [[TDKLF]], [[TDKSF]], [[TDKVF]], [[TDKWF]], [[UNS]], [[UNTRIM]], [[UNTRIM2007]], UNTRIM2 (SubGrid), [[UPDA2D]], [[VTDK]], [[WARM]]		\|preprocessor=[[DATACONVERT]], [[DIDAMERGE]], [[DIDAMINTZ]], [[DIDASPLIT]], [[ENERF]], [[FRQWF]], [[GRIDCONVERT]], [[LZKAF]], [[LZKMF]], [[LZKSF]], [[LZKVF]], [[LZKWF]], [[METDIDA]], [[PARTRACE]], [[POLWIND]], [[PGCALC]], [[TELEMAC-2D]], [[TM2DIDA]], [[TR2APP]], [[TR2DIDA]], [[TR3DIDA]], [[TDKLF]], [[TDKSF]], [[TDKVF]], [[TDKWF]], [[UNS]], [[UNTRIM]], [[UNTRIM2007]], UNTRIM2 (SubGrid), [[UPDA2D]], [[VTDK]], [[WARM]]
	\|postprocessor=[[EDITOR]]		\|postprocessor=[[EDITOR]]
	\|language=Fortran90		\|language=Fortran90

imported>Lang Guenther: version date changed

2016-02-24T12:43:05Z

version date changed

← Older revision		Revision as of 12:43, 24 February 2016
Line 2:		Line 2:
	\|name_de=HVIEW2D		\|name_de=HVIEW2D
	\|name=HVIEW2D		\|name=HVIEW2D
	\|version=~~September 2015~~		\|version=February 2016
	\|version_descr=October 2015		\|version_descr=October 2015
	\|catchwords=graphical postprocessor<br />		\|catchwords=graphical postprocessor<br />

imported>Seiss Guntram at 08:21, 12 October 2015

2015-10-12T08:21:49Z

← Older revision		Revision as of 08:21, 12 October 2015
Line 46:		Line 46:
	Besides an automatic presentation by HVIEW2D each figure can be manipulated in an interactive way by the user (deletion, shift, enlargement, reduction, insertion, ... of graphical objects).		Besides an automatic presentation by HVIEW2D each figure can be manipulated in an interactive way by the user (deletion, shift, enlargement, reduction, insertion, ... of graphical objects).

	If a user coordinate reference system is specified by BAWCRS all georeferenced information (mesh, structural lines and annotations, frames) will be transformed automatically into this system if the data contain their coordinate reference system. Therefor e.g files of type [[INSEL.DAT\|insel.dat]] have to be provided only in '''one (senseful)''' coordinate reference system. To use this feature the environment variable BAWCRS is set to the EPSG code of the preferred coordinate reference system, in which the pictures shall be viewed. Valid EPSG codes are found on page [[GEOTRANSFORMER]].		If a user coordinate reference system is specified by '''BAWCRS''' all georeferenced information (mesh, structural lines and annotations, frames) will be transformed automatically into this system if the data contain their coordinate reference system. Therefor e.g files of type [[INSEL.DAT\|insel.dat]] have to be provided only in '''one (senseful)''' coordinate reference system. To use this feature the environment variable BAWCRS is set to the EPSG code of the preferred coordinate reference system, in which the pictures shall be viewed. Valid EPSG codes are found on page [[GEOTRANSFORMER]].

	\|inputfiles=		\|inputfiles=

imported>Seiss Guntram: On the fly coordinate transformation into user coordinate system

2015-10-12T08:18:26Z

On the fly coordinate transformation into user coordinate system

← Older revision		Revision as of 08:18, 12 October 2015
Line 2:		Line 2:
	\|name_de=HVIEW2D		\|name_de=HVIEW2D
	\|name=HVIEW2D		\|name=HVIEW2D
	\|version=~~July 2012~~		\|version=September 2015
	\|version_descr=~~July 2012~~		\|version_descr=October 2015
	\|catchwords=graphical postprocessor<br />		\|catchwords=graphical postprocessor<br />
	finite element models<br />		finite element models<br />
Line 44:		Line 44:
	The geographical connexion of the data points is described on a grid topology. The grid consists out of arbitrary sized triangles. Areas which are falling dry for a certain period of time are properly taken into account as tidal flats compared to flooded areas where at the same time data are properly defined. If data have been created using program [[DIDASPLIT]], the existing script '''SplitScript''' (see ''Das Skript SplitScript in No. 3/1998'' of ''Supercomputing News''; available in German only) facilitates automated production of plotted results.		The geographical connexion of the data points is described on a grid topology. The grid consists out of arbitrary sized triangles. Areas which are falling dry for a certain period of time are properly taken into account as tidal flats compared to flooded areas where at the same time data are properly defined. If data have been created using program [[DIDASPLIT]], the existing script '''SplitScript''' (see ''Das Skript SplitScript in No. 3/1998'' of ''Supercomputing News''; available in German only) facilitates automated production of plotted results.

	Besides an automatic presentation by HVIEW2D each figure can be manipulated in an interactive way by the user (deletion, shift, enlargement, reduction, insertion, ... of graphical objects).		Besides an automatic presentation by HVIEW2D each figure can be manipulated in an interactive way by the user (deletion, shift, enlargement, reduction, insertion, ... of graphical objects).

			If a user coordinate reference system is specified by BAWCRS all georeferenced information (mesh, structural lines and annotations, frames) will be transformed automatically into this system if the data contain their coordinate reference system. Therefor e.g files of type [[INSEL.DAT\|insel.dat]] have to be provided only in '''one (senseful)''' coordinate reference system. To use this feature the environment variable BAWCRS is set to the EPSG code of the preferred coordinate reference system, in which the pictures shall be viewed. Valid EPSG codes are found on page [[GEOTRANSFORMER]].

	\|inputfiles=		\|inputfiles=
	# '''general input data''' (filetype [[HVIEW2D.DAT\|hview2d.dat]])		# '''general input data''' (filetype [[HVIEW2D.DAT\|hview2d.dat]])
Line 56:		Line 59:
	# definition of additional isolines for bathymetry (filetype [[ISOERG.DAT\|isoerg.dat]])		# definition of additional isolines for bathymetry (filetype [[ISOERG.DAT\|isoerg.dat]])
	# (optional) definition of '''static frames''' (filetype [[FRAMES.DAT\|frames.dat]])		# (optional) definition of '''static frames''' (filetype [[FRAMES.DAT\|frames.dat]])
	# (optional) '''structural lines''' (filetype [[INSEL.DAT\|insel.dat]])		# (optional) '''structural lines and annotations''' (filetype [[INSEL.DAT\|insel.dat]])
	# (optional) definition of desired '''points of time''' (filetype [[ZEITPUNKTE.DAT\|zeitpunkte.dat]])		# (optional) definition of desired '''points of time''' (filetype [[ZEITPUNKTE.DAT\|zeitpunkte.dat]])
	# (optional) company '''logo''' (filetype bawlogo.dat)		# (optional) company '''logo''' (filetype bawlogo.dat)

imported>Lang Guenther: configuration file for cfraction names added

2012-07-04T11:15:24Z

configuration file for cfraction names added

← Older revision		Revision as of 11:15, 4 July 2012
Line 2:		Line 2:
	\|name_de=HVIEW2D		\|name_de=HVIEW2D
	\|name=HVIEW2D		\|name=HVIEW2D
	\|version=~~10.x / January 2010~~		\|version=July 2012
	\|version_descr=~~January 2010~~		\|version_descr=July 2012
	\|catchwords=graphical postprocessor<br />		\|catchwords=graphical postprocessor<br />
	finite element models<br />		finite element models<br />
Line 65:		Line 65:
	For HVIEW2D the following standard configuration files from the directory''' $PROGHOME/cfg/''' are required:		For HVIEW2D the following standard configuration files from the directory''' $PROGHOME/cfg/''' are required:
	* GKS parameter file: '''gkssystem.computername.dat'''		* GKS parameter file: '''gkssystem.computername.dat'''
	* definition of physical quantities and physical units: '''phydef.cfg.~~deen~~.dat'''		* definition of physical quantities and physical units: '''phydef.cfg.de/en.dat''', '''phydef.cfg.rest.dat''', '''phydef.cfg.si.dat''', '''phydef-cf.cfg.dat'''
	* definition of hatching styles: '''hatch.cfg.dat'''		* definition of hatching styles: '''hatch.cfg.dat'''
			* DE/EN fraction names: '''fracdef.cfg.dat'
	\|outputfiles=		\|outputfiles=
	# '''graphical output''' to the screen		# '''graphical output''' to the screen

imported>BAWiki 2 at 10:57, 8 June 2010

2010-06-08T10:57:22Z

← Older revision		Revision as of 10:57, 8 June 2010
Line 26:		Line 26:

	The following methods of graphical presentation of data are actually integrated into HVIEW2D. Here comes a short list together with some example figures:		The following methods of graphical presentation of data are actually integrated into HVIEW2D. Here comes a short list together with some example figures:
	* coloured isosurface representation		* [[HVIEW2D - coloured isosurface representation\|coloured isosurface representation]]
	:* bathymetry		:* [[HVIEW2D - coloured isosurface representation#bathymetry\|bathymetry]]
	:* slack water time of flood current		:* [[HVIEW2D - coloured isosurface representation#slack water time of flood current\|slack water time of flood current]]
	:* tidal volume		:* [[HVIEW2D - coloured isosurface representation#tidal volume\|tidal volume]]
	:* maximum ebb current velocity		:* [[HVIEW2D - coloured isosurface representation#maximum ebb current velocity\|maximum ebb current velocity]]
	* isoline representation		* [[HVIEW2D - isoline representation\|isoline representation]]
	:* bathymetry		:* [[HVIEW2D - isoline representation#bathymetry\|bathymetry]]
	* vector representation		* [[HVIEW2D - vector representation\|vector representation]]
	:* maximum ebb current velocity		:* [[HVIEW2D - vector representation#maximum ebb current velocity\|maximum ebb current velocity ]]
	* hatching representation		* [[HVIEW2D - hatching representation\|hatching representation]]
	:* slack water time of flood current		:* [[HVIEW2D - hatching representation#slack water time of flood current\|slack water time of flood current]]
	:* tidal volume		:* [[HVIEW2D - hatching representation#tidal volume\|tidal volume]]
	:* maximum ebb current velocity		:* [[HVIEW2D - hatching representation#maximum ebb current velocity\|maximum ebb current velocity]]

	Construction as well as appearance of the data presented can be easily modified using different switches from within the application program in an interactive way by the user (see [[HVIEW2D:switches of the program HVIEW2D\|switches of the program HVIEW2D]]).		Construction as well as appearance of the data presented can be easily modified using different switches from within the application program in an interactive way by the user (see [[HVIEW2D:switches of the program HVIEW2D\|switches of the program HVIEW2D]]).

imported>BAWiki 2 at 15:47, 2 June 2010

2010-06-02T15:47:11Z

imported>BAWiki 3 at 10:32, 31 May 2010

2010-05-31T10:32:04Z

← Older revision		Revision as of 10:32, 31 May 2010
Line 79:		Line 79:
	In the course of the second processing step any polygon with assigned data may be optionally split at intersecting isolines into a series of smaller polygons. This kind of graphical data representation is much more expensive compared to the simplier shading of the original (unsplit) polygon but it is well suited to show more details of the data in areas with a small number of triangles.		In the course of the second processing step any polygon with assigned data may be optionally split at intersecting isolines into a series of smaller polygons. This kind of graphical data representation is much more expensive compared to the simplier shading of the original (unsplit) polygon but it is well suited to show more details of the data in areas with a small number of triangles.
	In the final processing stage all the data which have been assigned to the scene are converted into one of the several possible graphical representations (see also the examples given above).		In the final processing stage all the data which have been assigned to the scene are converted into one of the several possible graphical representations (see also the examples given above).
	\|preprocessor=[[DATACONVERT]], [[DIDAMERGE]], [[DIDAMINTZ]], [[DIDASPLIT]], [[ENERF]], [[FRQWF]], [[GRIDCONVERT]], [[LZKAF]], [[LZKMF]], [[LZKSF]], [[LZKVF]], [[LZKWF]], [[METDIDA]], [[PARTRACE]], [[PARTRACE-3D]], [[POLWIND]], [[PGCALC]], [[TELEMAC-2D]], [[TM2DIDA]], [[TR2APP]], [[TR2DIDA]], [[TR3DIDA]], [[TDKLF]], [[TDKSF]], [[TDKVF]], [[TDKWF]], [[UNS]], [[UNTRIM]], [[UNTRIM2007]], ~~UnTRIM2~~ (SubGrid), [[UPDA2D]], [[VTDK]], [[WARM]]		\|preprocessor=[[DATACONVERT]], [[DIDAMERGE]], [[DIDAMINTZ]], [[DIDASPLIT]], [[ENERF]], [[FRQWF]], [[GRIDCONVERT]], [[LZKAF]], [[LZKMF]], [[LZKSF]], [[LZKVF]], [[LZKWF]], [[METDIDA]], [[PARTRACE]], [[PARTRACE-3D]], [[POLWIND]], [[PGCALC]], [[TELEMAC-2D]], [[TM2DIDA]], [[TR2APP]], [[TR2DIDA]], [[TR3DIDA]], [[TDKLF]], [[TDKSF]], [[TDKVF]], [[TDKWF]], [[UNS]], [[UNTRIM]], [[UNTRIM2007]], UNTRIM2 (SubGrid), [[UPDA2D]], [[VTDK]], [[WARM]]
	\|postprocessor=[[EDITOR]]		\|postprocessor=[[EDITOR]]
	\|language=Fortran90		\|language=Fortran90

imported>BAWiki 3 at 10:31, 31 May 2010

2010-05-31T10:31:23Z

← Older revision		Revision as of 10:31, 31 May 2010
Line 47:		Line 47:
	\|inputfiles=		\|inputfiles=
	# '''general input data''' (filetype [[HVIEW2D.DAT\|hview2d.dat]])		# '''general input data''' (filetype [[HVIEW2D.DAT\|hview2d.dat]])
	# '''grid''' for 2D/3D-data (filetype [[GITTER05.DAT und GITTER05.BIN\|gitter05.dat/bin]] or [[~~SEFALIN~~\|selafin]] or [[UNTRIM_GRID.DAT\|untrim_grid.dat]] or [[UTRSUB_GRID.DAT\|utrsub_grid.dat]]) Notice: for 3D data sets with time varying bathymetry the depth values in the grid file must be equivalent to the depth of the non-erodible layer, whereas for corresponding 2D data sets values for actual depth are sufficient. In connexion with data sets defined for constant bathymetry the grid file must contain values for actual depth without exception.		# '''grid''' for 2D/3D-data (filetype [[GITTER05.DAT und GITTER05.BIN\|gitter05.dat/bin]] or [[SELAFIN\|selafin]] or [[UNTRIM_GRID.DAT\|untrim_grid.dat]] or [[UTRSUB_GRID.DAT\|utrsub_grid.dat]]) Notice: for 3D data sets with time varying bathymetry the depth values in the grid file must be equivalent to the depth of the non-erodible layer, whereas for corresponding 2D data sets values for actual depth are sufficient. In connexion with data sets defined for constant bathymetry the grid file must contain values for actual depth without exception.
	# '''list of edges''' (filetype [[FKVZ.BIN\|fkvz.bin]]) Notice: file will be automatically generated if not present		# '''list of edges''' (filetype [[FKVZ.BIN\|fkvz.bin]]) Notice: file will be automatically generated if not present
	# '''list of neighbour elements''' (filetype [[FKEZ.BIN\|fkez.bin]]) Notice: file will be automatically generated if not present		# '''list of neighbour elements''' (filetype [[FKEZ.BIN\|fkez.bin]]) Notice: file will be automatically generated if not present

← Older revision		Revision as of 10:31, 31 May 2010
Line 47:		Line 47:
	\|inputfiles=		\|inputfiles=
	# '''general input data''' (filetype [[HVIEW2D.DAT\|hview2d.dat]])		# '''general input data''' (filetype [[HVIEW2D.DAT\|hview2d.dat]])
	# '''grid''' for 2D/3D-data (filetype [[GITTER05.DAT und GITTER05.BIN\|gitter05.dat/bin]] or [[~~SEFALIN~~\|selafin]] or [[UNTRIM_GRID.DAT\|untrim_grid.dat]] or [[UTRSUB_GRID.DAT\|utrsub_grid.dat]]) Notice: for 3D data sets with time varying bathymetry the depth values in the grid file must be equivalent to the depth of the non-erodible layer, whereas for corresponding 2D data sets values for actual depth are sufficient. In connexion with data sets defined for constant bathymetry the grid file must contain values for actual depth without exception.		# '''grid''' for 2D/3D-data (filetype [[GITTER05.DAT und GITTER05.BIN\|gitter05.dat/bin]] or [[SELAFIN\|selafin]] or [[UNTRIM_GRID.DAT\|untrim_grid.dat]] or [[UTRSUB_GRID.DAT\|utrsub_grid.dat]]) Notice: for 3D data sets with time varying bathymetry the depth values in the grid file must be equivalent to the depth of the non-erodible layer, whereas for corresponding 2D data sets values for actual depth are sufficient. In connexion with data sets defined for constant bathymetry the grid file must contain values for actual depth without exception.
	# '''list of edges''' (filetype [[FKVZ.BIN\|fkvz.bin]]) Notice: file will be automatically generated if not present		# '''list of edges''' (filetype [[FKVZ.BIN\|fkvz.bin]]) Notice: file will be automatically generated if not present
	# '''list of neighbour elements''' (filetype [[FKEZ.BIN\|fkez.bin]]) Notice: file will be automatically generated if not present		# '''list of neighbour elements''' (filetype [[FKEZ.BIN\|fkez.bin]]) Notice: file will be automatically generated if not present

← Older revision		Revision as of 15:47, 2 June 2010
Line 19:		Line 19:
	\|shortdescription=The graphical postprocessor HVIEW2D can be used for a scaled graphical presentation of different scalar or vector quantities in the 2D horizontal plane. The data can be generated by means of different application programs. Either a single data set or a superposition of a scalar and a vector quantity can be plotted in several different ways.		\|shortdescription=The graphical postprocessor HVIEW2D can be used for a scaled graphical presentation of different scalar or vector quantities in the 2D horizontal plane. The data can be generated by means of different application programs. Either a single data set or a superposition of a scalar and a vector quantity can be plotted in several different ways.

	Results from two- as well as three-dimensional model simulations can be displayed. Truely three-dimensional data may be displayed for different layers (e.g. at the surface, at the bottom or at constant depth). ''For further informations ''see switches of the program HVIEW2D'' (working-level LEVEL_4).''		Results from two- as well as three-dimensional model simulations can be displayed. Truely three-dimensional data may be displayed for different layers (e.g. at the surface, at the bottom or at constant depth). For further informations see [[HVIEW2D:switches of the program HVIEW2D\|switches of the program HVIEW2D]] (working-level LEVEL_4).

	Also synoptic results based on a time-dependent topography can be displayed together with the correct bathymetric depth. In addition to that the three dimensional distribution for the sediments (e.g. fractions for various sediment classes) in the bottom can be also displayed.		Also synoptic results based on a time-dependent topography can be displayed together with the correct bathymetric depth. In addition to that the three dimensional distribution for the sediments (e.g. fractions for various sediment classes) in the bottom can be also displayed.
Line 40:		Line 40:
	:* maximum ebb current velocity		:* maximum ebb current velocity

	Construction as well as appearance of the data presented can be easily modified using different switches from within the application program in an interactive way by the user (see ''switches of the program HVIEW2D).''		Construction as well as appearance of the data presented can be easily modified using different switches from within the application program in an interactive way by the user (see [[HVIEW2D:switches of the program HVIEW2D\|switches of the program HVIEW2D]]).

	The geographical connexion of the data points is described on a grid topology. The grid consists out of arbitrary sized triangles. Areas which are falling dry for a certain period of time are properly taken into account as tidal flats compared to flooded areas where at the same time data are properly defined. If data have been created using program [[DIDASPLIT]], the existing script '''SplitScript''' (see ''Das Skript SplitScript in No. 3/1998'' of Supercomputing News; available in German only) facilitates automated production of plotted results.		The geographical connexion of the data points is described on a grid topology. The grid consists out of arbitrary sized triangles. Areas which are falling dry for a certain period of time are properly taken into account as tidal flats compared to flooded areas where at the same time data are properly defined. If data have been created using program [[DIDASPLIT]], the existing script '''SplitScript''' (see ''Das Skript SplitScript in No. 3/1998'' of ''Supercomputing News''; available in German only) facilitates automated production of plotted results.

	Besides an automatic presentation by HVIEW2D each figure can be manipulated in an interactive way by the user (deletion, shift, enlargement, reduction, insertion, ... of graphical objects).		Besides an automatic presentation by HVIEW2D each figure can be manipulated in an interactive way by the user (deletion, shift, enlargement, reduction, insertion, ... of graphical objects).
Line 71:		Line 71:
	# informative '''printer file''' (filetype hview2d.sdr)		# informative '''printer file''' (filetype hview2d.sdr)
	# (optional) plot''' metafiles''' (GKSM or CGM) and scale info file (hview2d???.gksm.scale or hview2d???.cgm.scale) for later calculation of geo-referenced coordinates		# (optional) plot''' metafiles''' (GKSM or CGM) and scale info file (hview2d???.gksm.scale or hview2d???.cgm.scale) for later calculation of geo-referenced coordinates
	# (optional) '''ASCII-version of displayed data''' (filetype [[OUTHVIEW2D.DAT\|outhview2d.dat]]) Notice: please observe significance of the switch '''OutAscii''' (on working level LEVEL_4).		# (optional) '''ASCII-version of displayed data''' (filetype [[OUTHVIEW2D.DAT\|outhview2d.dat]]) Notice: please observe significance of the [[HVIEW2D:switches of the program HVIEW2D\|switch]] '''OutAscii''' (on working level LEVEL_4).
	# (optional) '''trace''' of program execution (filetype hview2d.trc)		# (optional) '''trace''' of program execution (filetype hview2d.trc)
	# (optional) '''GKS-Logfile''' (filetype gkslog.dat) Notice: This file is used to record all interactive user input for a complete HVIEW2D application run. This file can be used at a later stage to rerun the whole session in exactly the same way. This can be profitably used to produce for example the same type of figures for a different set of data files.		# (optional) '''GKS-Logfile''' (filetype gkslog.dat) Notice: This file is used to record all interactive user input for a complete HVIEW2D application run. This file can be used at a later stage to rerun the whole session in exactly the same way. This can be profitably used to produce for example the same type of figures for a different set of data files.