TIMESHIFT - Revision history

Ak3gseis at 14:29, 10 October 2022

2022-10-10T14:29:30Z

← Older revision		Revision as of 14:29, 10 October 2022
Line 44:		Line 44:
	\|language=Fortran90		\|language=Fortran90
	\|add_software=-		\|add_software=-
	\|contact_original=~~[mailto:peter.schade@baw.de~~ P. Schade]		\|contact_original=P. Schade
	\|contact_maintenance=[mailto:~~peter~~.~~schade~~@baw.de ~~P. Schade~~]		\|contact_maintenance=[mailto:pre.proghome@baw.de working group PRE]
	\|documentation=please refer to $PROGHOME/examples/TimeShift/		\|documentation=please refer to $PROGHOME/examples/TimeShift/
	}}		}}

imported>BAWiki 3 at 06:55, 4 June 2010

2010-06-04T06:55:10Z

← Older revision		Revision as of 06:55, 4 June 2010
Line 22:		Line 22:
	Both methods are performed for all times of the actual time file. Thus, the output file contains the same number of times. Each of these datasets has the same internal temporal pattern. The modeller can select the dataset with the best fit from this ensemble.		Both methods are performed for all times of the actual time file. Thus, the output file contains the same number of times. Each of these datasets has the same internal temporal pattern. The modeller can select the dataset with the best fit from this ensemble.
	\|inputfiles=		\|inputfiles=
	# general input data (file of type [[TIMESHIFT.DAT\|~~Timeshift~~.dat]]);		# general input data (file of type [[TIMESHIFT.DAT\|timeshift.dat]]);
	# further input data is explained in the general input data mentioned above.		# further input data is explained in the general input data mentioned above.
	\|outputfiles=		\|outputfiles=

imported>BAWiki 3 at 06:53, 4 June 2010

2010-06-04T06:53:32Z

← Older revision		Revision as of 06:53, 4 June 2010
Line 39:		Line 39:
	The actual time file is allowed to contain several sub profiles. But one of them must have the same name and the same number of points as the single profile of the target time file. The depth values of the profiles are allowed to differ.		The actual time file is allowed to contain several sub profiles. But one of them must have the same name and the same number of points as the single profile of the target time file. The depth values of the profiles are allowed to differ.

	For application programmers: ~~TimeShift~~ uses the Fortran 90 packages io_dataset which also supports non-BDF formats. But only reading and writing of BDF files has been tested and released for general use.		For application programmers: TIMESHIFT uses the Fortran 90 packages io_dataset which also supports non-BDF formats. But only reading and writing of BDF files has been tested and released for general use.
	\|preprocessor=[[ADCP2PROFILE]], [[DIDAMERGE]], [[TICLQ2]], [[UNTRIM]], [[XTRLQ2]]		\|preprocessor=[[ADCP2PROFILE]], [[DIDAMERGE]], [[TICLQ2]], [[UNTRIM]], [[XTRLQ2]]
	\|postprocessor=[[GVIEW2D]], [[LQ2PRO]], [[VVIEW2D]], [[XTRDATA]]		\|postprocessor=[[GVIEW2D]], [[LQ2PRO]], [[VVIEW2D]], [[XTRDATA]]

imported>BAWiki 3 at 09:32, 28 May 2010

2010-05-28T09:32:44Z

← Older revision		Revision as of 09:32, 28 May 2010
Line 40:		Line 40:

	For application programmers: TimeShift uses the Fortran 90 packages io_dataset which also supports non-BDF formats. But only reading and writing of BDF files has been tested and released for general use.		For application programmers: TimeShift uses the Fortran 90 packages io_dataset which also supports non-BDF formats. But only reading and writing of BDF files has been tested and released for general use.
	\|preprocessor=[[[[ADCP2PROFILE]], [[DIDAMERGE]], [[TICLQ2]], [[UNTRIM]], [[XTRLQ2]]]]		\|preprocessor=[[ADCP2PROFILE]], [[DIDAMERGE]], [[TICLQ2]], [[UNTRIM]], [[XTRLQ2]]
	\|postprocessor=[[[[GVIEW2D]], [[LQ2PRO]], [[VVIEW2D]], [[XTRDATA]]]]		\|postprocessor=[[GVIEW2D]], [[LQ2PRO]], [[VVIEW2D]], [[XTRDATA]]
	\|language=Fortran90		\|language=Fortran90
	\|add_software=-		\|add_software=-

imported>BAWiki 3: Created page with '{{ProgramDescription |name_de=TIMESHIFT |name=TIMESHIFT |version=1.1 |version_descr=December 2008 |catchwords=ADCP moving ship measurement
comparison of measurement and mod…'

2010-05-28T09:32:03Z

Created page with '{{ProgramDescription |name_de=TIMESHIFT |name=TIMESHIFT |version=1.1 |version_descr=December 2008 |catchwords=ADCP moving ship measurement comparison of measurement and mod…'

New page

{{ProgramDescription
|name_de=TIMESHIFT
|name=TIMESHIFT
|version=1.1
|version_descr=December 2008
|catchwords=ADCP moving ship measurement 
comparison of measurement and model 
profile 
correction / shifting of data in time 
actual time 
target time
|shortdescription=The program TIMESHIFT performs a correction in time of model results on profile data. This improves the comparibility between model results and measurements for long profiles. Target times taken from an ADCP moving ship measurement are necessary for this purpose. They are computed from the mean measurement time and the measure time difference relative desired time with desired time meaning the mean measurement time. The time difference has to be available for each data point of the profile. The program ADCP2PROFILE generates this data.

The model result files are called actual time files from now on, whereas the measured data is contained in the target file. TIMESHIFT corrects all actual times in a two step procedure. The first step is the addition of the location dependant time difference relative desired time at every location. The dataset, which has the smallest difference towards the new target time, gets selected. Its values of the measure are stored for that location.

[http://www.baw.de/downloads/wasserbau/mathematische_verfahren/programmkennbl_de/pdf/TimeShift_20020515.pdf Fig.1: Profile after the first step of the correction in time. Model results and measurement display the same differences relative to their mean times (133k)]]

The second step is the optional addition of a constant time span. This enables the program to shift the actual time data exactly to the target time, even when actual and target time differ several years. The time span is computed out of the mean measure time and the estimated actual time, which is the time with probably the best fit of measurement and model. A value can be assigned to the estimated time in the general input data.

[http://www.baw.de/downloads/wasserbau/mathematische_verfahren/programmkennbl_de/pdf/TimeShift_to20060927.pdf Fig.2: The second step is an optional, constant shift in time. (133k)]]

Both methods are performed for all times of the actual time file. Thus, the output file contains the same number of times. Each of these datasets has the same internal temporal pattern. The modeller can select the dataset with the best fit from this ensemble.
|inputfiles=
# general input data (file of type [[TIMESHIFT.DAT|Timeshift.dat]]);
# further input data is explained in the general input data mentioned above.
|outputfiles=
# output data is explained in the general input data mentioned above;
# lineprinter file containing useful information related to program execution (filetype Timeshift.sdr);
# optional file with trace of program execution (filetype Timeshift.trc).
|methodology=
The correction changes only the temporal mapping. The further attributes of the actual time files are passed to the output file without change.

Values with a big time difference would be interpolated at the first or last time of the actual time file, which would give a wrong impression. In order to avoid this, the interpolated values at the first or last time are not used. They are marked as null values and will be displayed in grey coulor.

[http://www.baw.de/downloads/wasserbau/mathematische_verfahren/programmkennbl_de/pdf/TimeShift_Nullvalue.pdf Fig.3: Profile with null values displayed in grey. At these locations the corrections leaves the time span of the actual times. (133k)]]

Furthermore figure 3 displays the temporal mapping to the actual times. In order to demonstrate the effect, the interval is rather long (1 hour). There is obviously an discontinuity in the waterlevel at the intersection from one point in time to the next.

The actual time file is allowed to contain several sub profiles. But one of them must have the same name and the same number of points as the single profile of the target time file. The depth values of the profiles are allowed to differ.

For application programmers: TimeShift uses the Fortran 90 packages io_dataset which also supports non-BDF formats. But only reading and writing of BDF files has been tested and released for general use.
|preprocessor=[[[[ADCP2PROFILE]], [[DIDAMERGE]], [[TICLQ2]], [[UNTRIM]], [[XTRLQ2]]]]
|postprocessor=[[[[GVIEW2D]], [[LQ2PRO]], [[VVIEW2D]], [[XTRDATA]]]]
|language=Fortran90
|add_software=-
|contact_original=[mailto:peter.schade@baw.de P. Schade]
|contact_maintenance=[mailto:peter.schade@baw.de P. Schade]
|documentation=please refer to $PROGHOME/examples/TimeShift/
}}

TIMESHIFT - Revision history

Ak3gseis at 14:29, 10 October 2022

imported>BAWiki 3 at 06:55, 4 June 2010

imported>BAWiki 3 at 06:53, 4 June 2010

imported>BAWiki 3 at 09:32, 28 May 2010

imported>BAWiki 3: Created page with '{{ProgramDescription |name_de=TIMESHIFT |name=TIMESHIFT |version=1.1 |version_descr=December 2008 |catchwords=ADCP moving ship measurement comparison of measurement and mod…'

imported>BAWiki 3: Created page with '{{ProgramDescription |name_de=TIMESHIFT |name=TIMESHIFT |version=1.1 |version_descr=December 2008 |catchwords=ADCP moving ship measurement
comparison of measurement and mod…'