EVENTFILTER - Revision history

Ak3gseis at 12:52, 10 October 2022

2022-10-10T12:52:00Z

← Older revision		Revision as of 12:52, 10 October 2022
Line 72:		Line 72:
	\|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=$PROGHOME/examples/Frqwf/		\|documentation=$PROGHOME/examples/Frqwf/
	}}		}}

imported>BAWiki 3 at 08:59, 2 June 2010

2010-06-02T08:59:09Z

← Older revision		Revision as of 08:59, 2 June 2010
Line 23:		Line 23:

	\|outputfiles=		\|outputfiles=
	# file(s) containing a table with the statistics of a single station (type [[EVENTSTATISTIC.~~DAT and EVENTSTATISTIC~~.EXCEL\|eventstatistic.dat]] (ASCII) or ~~[[EVENTSTATISTIC.DAT and EVENTSTATISTIC.EXCEL\|~~eventstatistic.excel]]		# file(s) containing a table with the statistics of a single station (type [http://www.baw.de/methoden_en/index.php5/EVENTSTATISTIC.DAT_and_EVENTSTATISTIC.EXCEL eventstatistic.dat (ASCII) or eventstatistic.excel (excel compatibly)])
	#: (excel compatibly))
	# informative printer file (eventFilter.sdr)		# informative printer file (eventFilter.sdr)
	# (optional) trace of program execution (filetype eventFilter.trc)<br /><br />		# (optional) trace of program execution (filetype eventFilter.trc)<br /><br />

imported>BAWiki 3 at 09:35, 26 May 2010

2010-05-26T09:35:11Z

← Older revision		Revision as of 09:35, 26 May 2010
Line 64:		Line 64:

	Example: The daily mean fresh water flow at Neu Darchau in the Elbe estuary is shown in the upper part of the picture above. The values 200m3/s and 800m3/s limit the filter. E2 is the first event that lays inside these boundaries and that gets marked.		Example: The daily mean fresh water flow at Neu Darchau in the Elbe estuary is shown in the upper part of the picture above. The values 200m3/s and 800m3/s limit the filter. E2 is the first event that lays inside these boundaries and that gets marked.
	The lower diagram shows the high and low water events at Hamburg St. Pauli ~~87km~~ downstream from Neu Darchau. The events Tnw3, Thw3, Tnw4 and Thw4 are marked because they take place within 24 h after the marked event E2.		The lower diagram shows the high and low water events at Hamburg St. Pauli 87 km downstream from Neu Darchau. The events Tnw3, Thw3, Tnw4 and Thw4 are marked because they take place within 24 h after the marked event E2.

	====Combination of both filters====		====Combination of both filters====
	If you combine both filters the data is at first processed by the coupled band-pass and then by the fresh water flow filter. The combination works similar to a series connection. As a consequence the results in [[EVENTSTATISTIC.DAT~~\|eventstatistic.dat]]~~ and [[EVENTSTATISTIC.EXCEL\|eventstatistic.excel]] named '*_Q' are based on events that have been marked in '''both''' filters.		If you combine both filters the data is at first processed by the coupled band-pass and then by the fresh water flow filter. The combination works similar to a series connection. As a consequence the results in [[EVENTSTATISTIC.DAT and EVENTSTATISTIC.EXCEL\|eventstatistic.dat/.excel]] named '*_Q' are based on events that have been marked in '''both''' filters.

	\|preprocessor=-		\|preprocessor=-

imported>BAWiki 3 at 09:22, 26 May 2010

2010-05-26T09:22:59Z

← Older revision		Revision as of 09:22, 26 May 2010
Line 23:		Line 23:

	\|outputfiles=		\|outputfiles=
	# file(s) containing a table with the statistics of a single station (type [[EVENTSTATISTIC.DAT ~~und~~ EVENTSTATISTIC.EXCEL\|eventstatistic.dat]] (ASCII) or [[EVENTSTATISTIC.DAT ~~und~~ EVENTSTATISTIC.EXCEL\|eventstatistic.excel]]		# file(s) containing a table with the statistics of a single station (type [[EVENTSTATISTIC.DAT and EVENTSTATISTIC.EXCEL\|eventstatistic.dat]] (ASCII) or [[EVENTSTATISTIC.DAT and EVENTSTATISTIC.EXCEL\|eventstatistic.excel]]
	#: (excel compatibly))		#: (excel compatibly))
	# informative printer file (eventFilter.sdr)		# informative printer file (eventFilter.sdr)

imported>BAWiki 3 at 09:22, 26 May 2010

2010-05-26T09:22:28Z

← Older revision		Revision as of 09:22, 26 May 2010
Line 23:		Line 23:

	\|outputfiles=		\|outputfiles=
	# file(s) containing a table with the statistics of a single station (type [[EVENTSTATISTIC.DAT EVENTSTATISTIC.EXCEL\|eventstatistic.dat]] (ASCII) or [[EVENTSTATISTIC.DAT EVENTSTATISTIC.EXCEL\|eventstatistic.excel]]		# file(s) containing a table with the statistics of a single station (type [[EVENTSTATISTIC.DAT und EVENTSTATISTIC.EXCEL\|eventstatistic.dat]] (ASCII) or [[EVENTSTATISTIC.DAT und EVENTSTATISTIC.EXCEL\|eventstatistic.excel]]
	#: (excel compatibly))		#: (excel compatibly))
	# informative printer file (eventFilter.sdr)		# informative printer file (eventFilter.sdr)

imported>BAWiki 3 at 08:35, 26 May 2010

2010-05-26T08:35:21Z

← Older revision		Revision as of 08:35, 26 May 2010
Line 23:		Line 23:

	\|outputfiles=		\|outputfiles=
	# file(s) containing a table with the statistics of a single station (type [[EVENTSTATISTIC.DAT ~~and~~ EVENTSTATISTIC.EXCEL\|eventstatistic.dat]] (ASCII) or [[EVENTSTATISTIC.DAT ~~and~~ EVENTSTATISTIC.EXCEL\|eventstatistic.excel]]		# file(s) containing a table with the statistics of a single station (type [[EVENTSTATISTIC.DAT EVENTSTATISTIC.EXCEL\|eventstatistic.dat]] (ASCII) or [[EVENTSTATISTIC.DAT EVENTSTATISTIC.EXCEL\|eventstatistic.excel]]
	#: (excel compatibly))		#: (excel compatibly))
	# informative printer file (eventFilter.sdr)		# informative printer file (eventFilter.sdr)

imported>BAWiki 3 at 08:14, 26 May 2010

2010-05-26T08:14:30Z

← Older revision		Revision as of 08:14, 26 May 2010
Line 23:		Line 23:

	\|outputfiles=		\|outputfiles=
	# file(s) containing a table with the statistics of a single station (type [[EVENTSTATISTIC.DAT or EVENTSTATISTIC.EXCEL\|eventstatistic.dat]] (ASCII) or [[EVENTSTATISTIC.DAT or EVENTSTATISTIC.EXCEL\|eventstatistic.excel]]		# file(s) containing a table with the statistics of a single station (type [[EVENTSTATISTIC.DAT and EVENTSTATISTIC.EXCEL\|eventstatistic.dat]] (ASCII) or [[EVENTSTATISTIC.DAT and EVENTSTATISTIC.EXCEL\|eventstatistic.excel]]
	#: (excel compatibly))		#: (excel compatibly))
	# informative printer file (eventFilter.sdr)		# informative printer file (eventFilter.sdr)

imported>BAWiki 3 at 10:08, 11 May 2010

2010-05-11T10:08:55Z

← Older revision		Revision as of 10:08, 11 May 2010
Line 10:		Line 10:
	filter considering fresh water flow<br />		filter considering fresh water flow<br />
	desired and actual value<br />		desired and actual value<br />
	\|shortdescription=In order to analyse time series of high water or low water events you usually calculate their annual mean values. These values are influenced by meteorologic processes e.g. wind or fresh water flow in an estuary. This makes it difficult to compare the mean values of several years. The program ~~eventFilter~~ reduces the meteorologic influence by filtering the events and generates means you can better compare with each other.		\|shortdescription=In order to analyse time series of high water or low water events you usually calculate their annual mean values. These values are influenced by meteorologic processes e.g. wind or fresh water flow in an estuary. This makes it difficult to compare the mean values of several years. The program EVENTFILTER reduces the meteorologic influence by filtering the events and generates means you can better compare with each other.
	The input values are filtered by a [[#Coupled band-pass\|coupled band-pass]] and / or under consideration of the [[#Filter considering fresh water flow\|fresh water flow]].<br />		The input values are filtered by a [[#Coupled band-pass\|coupled band-pass]] and / or under consideration of the [[#Filter considering fresh water flow\|fresh water flow]].<br />
	\|inputfiles=		\|inputfiles=

imported>Mueller-hagedorn at 09:19, 11 May 2010

2010-05-11T09:19:09Z

← Older revision		Revision as of 09:19, 11 May 2010
Line 45:		Line 45:
	The algorithm for nipp tides works analogously.		The algorithm for nipp tides works analogously.

	[http://www.baw.de/downloads/wasserbau/mathematische_verfahren/programmkennbl_de/pdf/helgoland_bandpass.pdf Coupled band-pass Helgoland]		[http://www.baw.de/downloads/wasserbau/mathematische_verfahren/programmkennbl_de/pdf/helgoland_bandpass.pdf Example: Coupled band-pass Helgoland]

	The diagram shows the described case. Thw1 has been marked by the filter though it has a high value. The tide calender confirms the supposition that it takes place during a spring tide period. Thw2 and Thw3 are marked because they are inside the limits. Thw4 is without astronomical cause to low and has not been marked.		The diagram shows the described case. Thw1 has been marked by the filter though it has a high value. The tide calender confirms the supposition that it takes place during a spring tide period. Thw2 and Thw3 are marked because they are inside the limits. Thw4 is without astronomical cause to low and has not been marked.

imported>Mueller-hagedorn at 09:17, 11 May 2010

2010-05-11T09:17:39Z

← Older revision		Revision as of 09:17, 11 May 2010
Line 23:		Line 23:

	\|outputfiles=		\|outputfiles=
	# file(s) containing a table with the statistics of a single station (type [[EVENTSTATISTIC.DAT\|eventstatistic.dat]] (ASCII) or [[EVENTSTATISTIC.EXCEL\|eventstatistic.excel]]		# file(s) containing a table with the statistics of a single station (type [[EVENTSTATISTIC.DAT or EVENTSTATISTIC.EXCEL\|eventstatistic.dat]] (ASCII) or [[EVENTSTATISTIC.DAT or EVENTSTATISTIC.EXCEL\|eventstatistic.excel]]
	#: (excel compatibly))		#: (excel compatibly))
	# informative printer file (eventFilter.sdr)		# informative printer file (eventFilter.sdr)
Line 31:		Line 31:

	====Preparations====		====Preparations====
	The reference station should be situated in an area with few meteorological influence on high water and low water. In the German Bight Helgoland would be a suited place. At first ~~eventFilter~~ has to identify a reference event as high water or low water. You get the best results by analyzing the synthetic values. ~~EventFilter~~ compares date and time of a measured event with date and time of a neighboured synthetic event and identifies the actual high and low water events.		The reference station should be situated in an area with few meteorological influence on high water and low water. In the German Bight Helgoland would be a suited place. At first EVENTFILTER has to identify a reference event as high water or low water. You get the best results by analyzing the synthetic values. EVENTFILTER compares date and time of a measured event with date and time of a neighboured synthetic event and identifies the actual high and low water events.
	(All events in the following pictures are linear connected and therefore not realistically represented.)		(All events in the following pictures are linear connected and therefore not realistically represented.)

	[~~[File~~:~~Soll_ist_small~~.~~png‎]~~]		[http://www.baw.de/downloads/wasserbau/mathematische_verfahren/programmkennbl_de/pdf/helgoland_soll_ist.pdf Example: Helgoland desired and actual value]

			The picture above shows that the identification works well even in the case of a storm flood. The water level differs between the synthetic red curve and the measured green curve up to 2 meters, whereas the time always differs less than an hour.
	~~desired and actual value at the reference~~ The picture above shows that the identification works well even in the case of a storm flood. The water level differs between the synthetic red curve and the measured green curve up to 2 meters, whereas the time always differs less than an hour.

	The second way to identify high and low water is to use the mean flood period at the reference station. It should only be used if there are no synthetic values available.		The second way to identify high and low water is to use the mean flood period at the reference station. It should only be used if there are no synthetic values available.
Line 46:		Line 45:
	The algorithm for nipp tides works analogously.		The algorithm for nipp tides works analogously.

	[~~[File~~:~~Bandpass_small~~.~~png‎]~~]		[http://www.baw.de/downloads/wasserbau/mathematische_verfahren/programmkennbl_de/pdf/helgoland_bandpass.pdf Coupled band-pass Helgoland]

	~~bandpass at the reference~~ The diagram shows the described case. Thw1 has been marked by the filter though it has a high value. The tide calender confirms the supposition that it takes place during a spring tide period. Thw2 and Thw3 are marked because they are inside the limits. Thw4 is without astronomical cause to low and has not been marked.		The diagram shows the described case. Thw1 has been marked by the filter though it has a high value. The tide calender confirms the supposition that it takes place during a spring tide period. Thw2 and Thw3 are marked because they are inside the limits. Thw4 is without astronomical cause to low and has not been marked.
	Tnw1 has been marked because Thw1 is to high. Tnw2 to Tnw4 are to low.		Tnw1 has been marked because Thw1 is to high. Tnw2 to Tnw4 are to low.

Line 61:		Line 60:
	The water level in the upstream region of an estuary is highly influenced by the amount of fresh water flow. But in other areas the water level is influenced by extremly high or low amounts, too. Therefore water flow measurements between a lower and upper limit are marked. The corresponding high and low water events are marked as well and their mean values get calculated.		The water level in the upstream region of an estuary is highly influenced by the amount of fresh water flow. But in other areas the water level is influenced by extremly high or low amounts, too. Therefore water flow measurements between a lower and upper limit are marked. The corresponding high and low water events are marked as well and their mean values get calculated.

	[~~[File~~:~~Oberwasserfilter_small~~.~~png‎]~~]		[http://www.baw.de/downloads/wasserbau/mathematische_verfahren/programmkennbl_de/pdf/stpauli_oberwasser.pdf Example: fresh water flow and high/low water]


	~~fresh water flow and high / low water~~ Example: The daily mean fresh water flow at Neu Darchau in the Elbe estuary is shown in the upper part of the picture above. The values 200m3/s and 800m3/s limit the filter. E2 is the first event that lays inside these boundaries and that gets marked.		Example: The daily mean fresh water flow at Neu Darchau in the Elbe estuary is shown in the upper part of the picture above. The values 200m3/s and 800m3/s limit the filter. E2 is the first event that lays inside these boundaries and that gets marked.
	The lower diagram shows the high and low water events at Hamburg St. Pauli 87km downstream from Neu Darchau. The events Tnw3, Thw3, Tnw4 and Thw4 are marked because they take place within 24 h after the marked event E2.		The lower diagram shows the high and low water events at Hamburg St. Pauli 87km downstream from Neu Darchau. The events Tnw3, Thw3, Tnw4 and Thw4 are marked because they take place within 24 h after the marked event E2.