PTAGISWiki - Recent changes [en]

SOP: Add a new Obs Site definition

Davem — Fri, 03 Sep 2010 01:37:01 GMT

Added Obs_ Site_ Location_ Info caveat

←Older revision		Revision as of 01:37, 3 September 2010
(One intermediate revision not shown.)
Line 44:		Line 44:

	10) If the site is a "small-stream" or "adult ladder" detection site, then:		10) If the site is a "small-stream" or "adult ladder" detection site, then:
-	* If the site is a "small-stream" detection site (ref_code in {2,3,6,8} in ptagis3.master_site_code_definitions, where the domain = 'OBS SITE TYPE'), then add an option to the site selection menu in the '~www/ptoccentral/dbaccess/InStrmDtctn/InStrmDtctn_form.html' file, and add a description to the '~www/ptoccentral/dbaccess/InStrmDtctn/InStrmDtctn_null.html' file.	+	* If the site is a "small-stream" detection site (ref_code in {2,3,6} in ptagis3.master_site_code_definitions, where the domain = 'OBS SITE TYPE'), then add an option to the site selection menu in the '~www/ptoccentral/dbaccess/InStrmDtctn/InStrmDtctn_form.html' file, and add a description to the '~www/ptoccentral/dbaccess/InStrmDtctn/InStrmDtctn_null.html' file.
	* If the site is an "adult ladder" detection site (ref_code = 7 in ptagis3.master_site_code_definitions, where the domain = 'OBS SITE TYPE'), then add an option to the site selection menu in the '~www/ptoccentral/dbaccess/adreturn/AdReturn_form.html' file, and add a verbose site description to the '~www/ptoccentral/dbaccess/adreturn/AdReturn_null.html' file.		* If the site is an "adult ladder" detection site (ref_code = 7 in ptagis3.master_site_code_definitions, where the domain = 'OBS SITE TYPE'), then add an option to the site selection menu in the '~www/ptoccentral/dbaccess/adreturn/AdReturn_form.html' file, and add a verbose site description to the '~www/ptoccentral/dbaccess/adreturn/AdReturn_null.html' file.
		+	* If the site is a "hatchery adult return" detection site (ref_code = 8 in ptagis3.master_site_code_definitions, where the domain = 'OBS SITE TYPE'), then add an option to the site selection menu in the '~www/ptoccentral/dbaccess/adreturn/HatReturn_form.html' file, and add a verbose site description to the '~www/ptoccentral/dbaccess/adreturn/HatReturn_null.html' file.

	11) Add Data Steward contact information (and POC and other contacts, as necessary) to the Obs_Site_Contacts table.		11) Add Data Steward contact information (and POC and other contacts, as necessary) to the Obs_Site_Contacts table.
Line 56:		Line 57:
	</pre>		</pre>

-	13) Add a record to the Obs_Site_Location_Info table.	+	13) Add a record to the Obs_Site_Location_Info table.''To satisfy ALRS, all sites must be tied to a stream or river segment; don't attach to a hatchery or dam!''

	14) Run the appropriate in-stream or fixed-site SQL script to add the new definition to ALRS.		14) Run the appropriate in-stream or fixed-site SQL script to add the new definition to ALRS.

Warm Springs NFH

Stevepastor — Thu, 02 Sep 2010 21:09:25 GMT

As in 2009 Spec Doc

←Older revision		Revision as of 21:09, 2 September 2010
Line 20:		Line 20:
	:Jesse Rivera 360 604-2541		:Jesse Rivera 360 604-2541

-	Data Coordinator	+	Tag Data Coordinator
	:David Hand 360 604-2518		:David Hand 360 604-2518

Talk:Tag Data Coordinator

Stevepastor — Thu, 02 Sep 2010 21:01:08 GMT

start talk

New page

This is an effort to make information more accessible via the wiki pages.

It seems that the "Reference" html "tags" I am used to using are not enabled here. Most text should have a reference attached to establish credibility. [[User:Stevepastor|Stevepastor]] 14:01, 2 September 2010 (PDT)

Tag Data Coordinator

Stevepastor — Thu, 02 Sep 2010 20:57:51 GMT

reference

New page

All data submitted to PTAGIS are associated with a Tag Data Coordinator, who can be contacted in order to verify the integrity of those data.

All data in the PTAGIS database are assumed to be preliminary, and as such unsuitable for formal analysis and review, until and unless the appropriate Tag Data Coordinator verifies the integrity of those data.

Data users will contact the appropriate Tag Data Coordinator(s) prior to including, summarizing, or referencing those data in any publication other than for internal distribution. This includes both peer-reviewed and non-reviewed documents.<ref>2009 Spec Doc. Page 9.</ref>

BCC Automated Read Range Tester

Troy — Wed, 01 Sep 2010 16:16:05 GMT

Journal:

←Older revision		Revision as of 16:16, 1 September 2010
(3 intermediate revisions not shown.)
Line 36:		Line 36:

	[[User:Troy\|Troy]] 14:49, 24 February 2009 (PST)Testing in being conducted to optimize the unit. PSMFC is trying to minimize the time the unit is in the field by increasing the speed of the unit. The risk is that with higher speeds the likely hood of the unit over traveling becomes greater. Depending on where in the cycle an over travel occurs this can lead to even more time in the field than if the unit was ran slowly in and out as the unit has to correct it's self when an over travel occurs. Currently a the total time the unit could be in the field is determined by how long the tag is inside the shield for each test. 6.03 sec's proves to be fairly reliable. (4000+ test with no OT's) The fastest has been 4.8 sec but resulted in several over travels. Currently running at 5.48 sec. More information is available on [[Talk:BCC_Read_Range_Tester#2-24-2009\|ARRT Testing]]		[[User:Troy\|Troy]] 14:49, 24 February 2009 (PST)Testing in being conducted to optimize the unit. PSMFC is trying to minimize the time the unit is in the field by increasing the speed of the unit. The risk is that with higher speeds the likely hood of the unit over traveling becomes greater. Depending on where in the cycle an over travel occurs this can lead to even more time in the field than if the unit was ran slowly in and out as the unit has to correct it's self when an over travel occurs. Currently a the total time the unit could be in the field is determined by how long the tag is inside the shield for each test. 6.03 sec's proves to be fairly reliable. (4000+ test with no OT's) The fastest has been 4.8 sec but resulted in several over travels. Currently running at 5.48 sec. More information is available on [[Talk:BCC_Read_Range_Tester#2-24-2009\|ARRT Testing]]
		+
		+	[[User:Troy\|Troy]] 09:15, 1 September 2010 (PDT)<br>
		+	Results for the 2010 Season.
		+
		+	The counters for ARRT were reset on 4/5/2010 at 13:03. From that time until 9/1/2010 at 08:30 3668 tests were ran and 3405 result in a read greater than -30 inches.

	==Meeting Minutes==		==Meeting Minutes==