GeodesyLab - User contributions [en]

http://gps.alaska.edu/internal/api.php?action=feedcontributions&feedformat=atom&user=Yuning GeodesyLab - User contributions [en] 2026-04-16T00:08:33Z User contributions MediaWiki 1.25.1 http://gps.alaska.edu/internal/index.php?title=Fieldwork&diff=2893 Fieldwork 2011-10-10T20:18:00Z

<p>Yuning: </p> <hr /> <div>:''Reach site, hunt around,''<br /> :''Setup, precise centering,''<br /> :''Yellow box takes data.''<br /> ::''- A concise guide to GPS fieldwork''<br /> <br /> Perhaps the most important thing to remember about GPS fieldwork is that with a 24-hour GPS survey you can measure the position of the GPS antenna to within about 2 mm horizontal precision and 6 mm vertical precision, and you can measure the vector between two GPS antennas even more precisely than that. What this means is that the tolerances for setup error are very tight and you have to be very careful. If not, YOU are likely to be the limiting error source in the measurements. It also means that you really can't hide it if you screw up. So do your best if you make a mistake or something odd happens, carefully record it on the log sheet. It is far better to know we have a bad observation than to find out years later.<br /> <br /> ===Where can I find site information?===<br /> We maintain a [http://gps.alaska.edu/gps GPS Site Database] that in theory stores site information from all the GPS sites we use. In practice, some are missing, but the database is mostly complete for Alaska and environs. You can search the database by 4 characeter ID, or radial or rectangular searches, and other ways as well. To access the database, you need a login and password, and for that you need to ask Jeff.<br /> <br /> ===Where to find Julian Day Calendar===<br /> Here is printable Julian Day Calendar: [http://gps.alaska.edu/~yuning/JulianDayCalendar.pdf Julian Day]<br /> <br /> ===Information Sign===<br /> Here is a digital copy of the sign that you put on your GPS setups to inform people what it is and ask them not to disturb the setup: [http://gps.alaska.edu/~yuning/Sign.pdf sign].<br /> <br /> ===Traveling in Alaska===<br /> <br /> Before you go on official University travel be sure to fill out a Travel Authorization (TA) form. You can get this from Candice Lake on the 6th floor in the buisness office. Even if you do not expect to spend money on the trip, it is important that you fill out this form for insurance purposes. When you return it is necessary to fill out an expense report (to be sure you are reimbursed for incurred costs), even if you had no expenses.<br /> <br /> <b>Rental Cars</b><br><br /> A rental is often the cheapest way to travel on the road network in Alaska. If you are traveling on University buisness (fieldwork falls in this <br /> category) then the university covers the insurance, be sure to decline coverage when renting the car. Be sure to print [http://gps.alaska.edu/tfour/Misc/travel_papers.pdf this document] when traveling in a rental car; it contains [http://gps.alaska.edu/tfour/Misc/travel_papers.pdf proof of insurance] and some phone numbers to call if an accident occurs. The GI recommends that you '''not''' rent from Budget due to their aggressive collection agency should damages occur to the vehicle while in your possesion. The GI recommends using [http://www.avis.com Avis] or some other rental company. Do not rent from the airport rental location, there is an additional 10% tax plus fees added to the price of rental if you rent from the airport. Most of the rental companies have other locations in town, which have lower costs. <br /> <br /> <b>Flying in the Bush</b><br><br /> This is not your regular commercial flight, get all the information you need prior to departure.<br /> <br /> <br /> ===How to set up a tripod===<br /> <br /> There are as many different explanations as people who have set up a tripod before. Well, one description you can use is this: Follow the link to a printable [http://www.gps.alaska.edu/tfour/Misc/tripodsetup1.pdf setup description] and/or the link to [[new site and tripod setup description]].<br /> <br /> ===How to set up a spike mount===<br /> 1) Locate benchmark with hand-held GPS or site description.<br /> <br /> 2) Assemble spike mount by attaching legs to spike.<br /> a. *Out of the case the legs on the spike mount will be short. Use the leg extensions as needed to improve stability.<br /> b. Additional wing-nuts, lock washers and spike tips are included in the case<br /> 3) Set the spike on the benchmark with the legs oriented at 90 degrees from each other, or as close to 90 as possible.<br /> <br /> 4) Loosely tighten the wing-nut on the leg extensions to hold the leg lengths.<br /> <br /> 5) Use the carpenter’s level and the leg screws to level each leg independently.<br /> <br /> 6) Loosen the wing nuts and add weights (rocks) to hold the leg positions, retighten the wing nuts.<br /> <br /> 7) Attach the leveling plate to the spike and place the bull’s-eye level on the plate.<br /> <br /> 8) Use the leg screw to level the plate. Once the plate is level tighten the locking nut on the legs.<br /> <br /> 9) Remove the leveling plate.<br /> <br /> 10) Attach the antenna to the spike. ** Do not attach the antenna cable yet.**<br /> a. Make sure at least one spike clamp is tight, to ensure that the spike doesn’t rotate when tightening the antenna.<br /> 11) Orient the antenna to north.<br /> a. Set the declination on your compass, the compass can be placed directly onto the antenna. <br /> b. Some antennas are marked with a North arrow others are not. If there is no North direction indicated, Notch 1 <br /> (located at the edge on the antenna) should be pointed north.<br /> c. The antenna will likely need to be rotated. Loosen the spike clamps and rotate in the clockwise (tightening)<br /> direction.<br /> 12) Hook the receiver up to power.<br /> <br /> 13) Attach the antenna cable to receiver and antenna.<br /> <br /> ===Orienting the antenna to TRUE NORTH===<br /> Every antenna has a reference line or arrow that must be oriented toward TRUE NORTH. The reason for this is that the position actually measured by GPS is something called the ''antenna phase center'', which in general is not located on the axis of the antenna. So if you orient the antenna in some other direction, you introduce an error into the resulting postion that for many antennas is much larger than the measurement uncertainty.<br /> :The reference arrow for the Trimble 4000's antenna is marked on the antenna.<br /> :For other antennas, the antenna cable connector should point to NORTH. There will normally be something marked on the top of the antenna along that same line.<br /> <br /> To orient the antenna, you need to know the magnetic declination. It should be recorded on the site description. If not, it can be found on any USGS topo map. If all else fails, remember 25 degrees east, which is not too far off for most of central and southern Alaska.<br /> :If the declination is EAST, set your compass to 360 - declination and orient by the north arrow on the compass.<br /> :If the declination is WEST, set your compass to 360 + declination and orient by the north arrow on the compass.<br /> <br /> If you find that you oriented the antenna the wrong way, and it is already recording data, don't do anything rash! The best thing to do in this case is to carefully record the actual orientation of the antenna. <br /> <br /> ===Programming a Trimble 4000 receiver===<br /> You can find a printable description of a [http://www.gps.alaska.edu/tfour/Misc/ReceiverSetup_multiday.pdf multi-day receiver setup] by clicking on that link.<br /> <br /> ===Using the Trimble 5700 and R7 receivers===<br /> These two receivers are basically the same thing. Neither one is convenient to program in the field. Turn them on and they should work.<br /> <br /> What the lights mean.<br /> <br /> <br /> ===Using the Trimble Net-RS receiver===<br /> <br /> The main issue with the Net-RS receiver is that it writes all data for one UTC day into ONE file. This must be<br /> considered when a station is moved within one UTC day between sites. It is possible to untangle the data but still it's a hassle. In Alaska a new UTC day starts at 4:00 pm, meaning that taking the station down before 4 pm and setting it out somewhere else after 4 pm would be ideal.<br /> <br /> If you must visit 2 sites on the same Julian day, here is a way to get the data to go into separate files. You'll need a laptop, and a crossover (Xover) ethernet cable. Set your network settings on the laptop to IP: 192.168.1.3 NetMask: 255.255.255.0 Gateway: 192.168.1.1<br /> Connect the laptop to the NetRS. Open internet explorer or equiv. and go to the site 192.168.1.2<br /> The web interface should appear with a blue background. Under Data Logging, switch from one 30sec 24hour session to another by toggling the appropriate "enable" boxes. If you need to program a second campaign session, read the manual.<br /> <br /> ATTN: The Net-RS receiver has different power and antenna inputs! Make sure you have the right cables (usually they do not fit into the black case) before you leave the vehicle, especially when the site is away from the road.<br /> <br /> ===Using the Topcon GB-1000 receiver===<br /> There is printable introduction here: [http://gps.alaska.edu/~yuning/topcongb1000.pdf Topcon Guide]<br /> <br /> <br /> ===Using the Topcon RTK setup ===<br /> This deserves its own site [[Topcon RTK]]<br /> <br /> ===Downloading the Trimble 4000 receiver===<br /> <br /> 1. Get DOS Laptop<br /> <br /> 2. Boot and cd to C:\DOWNLOAD<br /> <br /> 3. Connect Serial Cable (Port I/0 1)<br /> <br /> 4. Connect power (either 12V car battery or adapter)<br /> <br /> 5. start program '4000': <code>C:\DOWNLOAD>4000</code><br /> <br /> 6. rename files according to Julian day<br /> <br /> 7. follow screen instructions (make sure connection rate is the same as in receiver)<br /> <br /> 8. get data on memory card<br /> <br /> 9. ftp data from memory card that should be pushed into a different computer to linux system<br /> <br /> ===Downloading the Trimble 5700 receiver===<br /> <br /> We will use the "Windows system" computer to download data from Trimber 5700 receiver. And also make sure that log sheet is at your hand.<br /> <br /> 1. Take the Trimble 5700 receiver out from the yellow box (I know it's "crap", but it's exact what we do first).<br /> <br /> 2. There are two cables needed to plug into the receiver: power cable (circle); data cable (a little bit rectangular). Power on the receiver.<br /> <br /> 3. Double click "Shortcut to DataXfer.exe" on the computer desktop. If the receiver is already connected, the software will display the receiver and its series number, check the number and what was recorded on the log sheet, make sure they are matched.<br /> <br /> 4. Click the "add" button, then you can see all the recorded data in the receiver. Choose the data you want to download, and make sure save the data file to directory E:\GPSdata\. For example, if we want to download compaign data of KENAI trip in 2008, the subdirectory can be created as E:\GPSdata\data 2008\campaign\kenai, and the downloaded data should go to there. Then, click "Transfer", then you will see the computer doing its work to download data. And you need to click "OK" during the download.<br /> <br /> 5. Change files name. Usually, there are two files for one day of one site: *.dat and *.T00. Change the first 4 letters to site name for both of these two files. For example, for site DAHL, the data file name should be changed to the format like this: "dahl1430.dat" and "dahl1430.T00" (143 is the Julian day). If the name of site has only 3 letters (site CPR, for example), then names should be like this: "cpr_1450.dat" and "cpr_1450.T01". <br /> <br /> 6. The download work is done. Power off receiver and put the receiver back to the yellow box. Check if all the stuff (receiver, antenna, power cable, data cable) is the box before you close it.<br /> <br /> Then you can go on downloading next receiver. You can re-start the software (Shortcut to DataXfer.exe), then it will detect the new receiver automatically.<br /> <br /> ===Downloading the Trimble Net-RS receiver===<br /> [TODO.]<br /> <br /> ===What goes on the data log sheet?===<br /> Data log sheets are used to record important information regarding the site/benchmark and the survey session. We record information about the site, such as the name, benchmark inscription, and location. It is important to log information about the equipment used; including serial numbers, and type of equipment. We record hieght information, direction, as well as time and duration of the survey. It is important to log who conducted the survey as well as any unusual things/mishaps that occured during the survey. Follow the link to a printable [http://www.gps.alaska.edu/tfour/Misc/Alaska_Log.pdf log sheet].<br /> <br /> ===Where do data log sheets go===<br /> In the filing cabinet, in a hanging file stored by GPS campaign.<br /> <br /> Every year, we send a copy of all log sheets to [http://www.unavco.org UNAVCO] for permanent archiving, along with the data files. Sometimes after a while it is easier to find the information from the [http://www.unavco.org/facility/data/data.html UNAVCO Data Archive] than it is to find our own log sheets in the filing cabinet.<br /> <br /> <br /> ===Converting files to RINEX===<br /> The final step in the fieldwork is to convert the data files to the RINEX format. RINEX stands for '''R'''eceiver '''IN'''dependent '''EX'''change format. It is an ASCII format that is publicly documented and agreed upon worldwide. In contrast, the Trimble .dat and .t00/.t01 files are proprietary formats that are only used by Trimble. Naturally, every receiver manufacturer has its own proprietary format. There is a more compact binary format called BINEX that is meant to store the same information. BINEX has been adopted as the standard format for [http://pbo.unavco.org PBO], and may one day become the standard instead of RINEX.<br /> <br /> There are enough steps in the process that [[RINEXing|a complete guide]] is on its own page.<br /> <br /> <br /> ===Field Notes===<br /> [[Field Notes]] on successful and not-so-successful field excursions may help you plan your next trip.</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Fieldwork&diff=2892 Fieldwork 2011-10-10T20:16:53Z

<p>Yuning: </p> <hr /> <div>:''Reach site, hunt around,''<br /> :''Setup, precise centering,''<br /> :''Yellow box takes data.''<br /> ::''- A concise guide to GPS fieldwork''<br /> <br /> Perhaps the most important thing to remember about GPS fieldwork is that with a 24-hour GPS survey you can measure the position of the GPS antenna to within about 2 mm horizontal precision and 6 mm vertical precision, and you can measure the vector between two GPS antennas even more precisely than that. What this means is that the tolerances for setup error are very tight and you have to be very careful. If not, YOU are likely to be the limiting error source in the measurements. It also means that you really can't hide it if you screw up. So do your best if you make a mistake or something odd happens, carefully record it on the log sheet. It is far better to know we have a bad observation than to find out years later.<br /> <br /> ===Where can I find site information?===<br /> We maintain a [http://gps.alaska.edu/gps GPS Site Database] that in theory stores site information from all the GPS sites we use. In practice, some are missing, but the database is mostly complete for Alaska and environs. You can search the database by 4 characeter ID, or radial or rectangular searches, and other ways as well. To access the database, you need a login and password, and for that you need to ask Jeff.<br /> <br /> ===Where to find Julian Day Calendar===<br /> Here is printable Julian Day Calendar: [http://gps.alaska.edu/~yuning/JulianDayCalendar.pdf Julian Day]<br /> <br /> ===Information Sign===<br /> Here is a digital copy of the sign that you put on your GPS setups to inform people what it is and ask them not to disturb the setup: [http://gps.alaska.edu/~yuning/Sign.pdf].<br /> <br /> ===Traveling in Alaska===<br /> <br /> Before you go on official University travel be sure to fill out a Travel Authorization (TA) form. You can get this from Candice Lake on the 6th floor in the buisness office. Even if you do not expect to spend money on the trip, it is important that you fill out this form for insurance purposes. When you return it is necessary to fill out an expense report (to be sure you are reimbursed for incurred costs), even if you had no expenses.<br /> <br /> <b>Rental Cars</b><br><br /> A rental is often the cheapest way to travel on the road network in Alaska. If you are traveling on University buisness (fieldwork falls in this <br /> category) then the university covers the insurance, be sure to decline coverage when renting the car. Be sure to print [http://gps.alaska.edu/tfour/Misc/travel_papers.pdf this document] when traveling in a rental car; it contains [http://gps.alaska.edu/tfour/Misc/travel_papers.pdf proof of insurance] and some phone numbers to call if an accident occurs. The GI recommends that you '''not''' rent from Budget due to their aggressive collection agency should damages occur to the vehicle while in your possesion. The GI recommends using [http://www.avis.com Avis] or some other rental company. Do not rent from the airport rental location, there is an additional 10% tax plus fees added to the price of rental if you rent from the airport. Most of the rental companies have other locations in town, which have lower costs. <br /> <br /> <b>Flying in the Bush</b><br><br /> This is not your regular commercial flight, get all the information you need prior to departure.<br /> <br /> <br /> ===How to set up a tripod===<br /> <br /> There are as many different explanations as people who have set up a tripod before. Well, one description you can use is this: Follow the link to a printable [http://www.gps.alaska.edu/tfour/Misc/tripodsetup1.pdf setup description] and/or the link to [[new site and tripod setup description]].<br /> <br /> ===How to set up a spike mount===<br /> 1) Locate benchmark with hand-held GPS or site description.<br /> <br /> 2) Assemble spike mount by attaching legs to spike.<br /> a. *Out of the case the legs on the spike mount will be short. Use the leg extensions as needed to improve stability.<br /> b. Additional wing-nuts, lock washers and spike tips are included in the case<br /> 3) Set the spike on the benchmark with the legs oriented at 90 degrees from each other, or as close to 90 as possible.<br /> <br /> 4) Loosely tighten the wing-nut on the leg extensions to hold the leg lengths.<br /> <br /> 5) Use the carpenter’s level and the leg screws to level each leg independently.<br /> <br /> 6) Loosen the wing nuts and add weights (rocks) to hold the leg positions, retighten the wing nuts.<br /> <br /> 7) Attach the leveling plate to the spike and place the bull’s-eye level on the plate.<br /> <br /> 8) Use the leg screw to level the plate. Once the plate is level tighten the locking nut on the legs.<br /> <br /> 9) Remove the leveling plate.<br /> <br /> 10) Attach the antenna to the spike. ** Do not attach the antenna cable yet.**<br /> a. Make sure at least one spike clamp is tight, to ensure that the spike doesn’t rotate when tightening the antenna.<br /> 11) Orient the antenna to north.<br /> a. Set the declination on your compass, the compass can be placed directly onto the antenna. <br /> b. Some antennas are marked with a North arrow others are not. If there is no North direction indicated, Notch 1 <br /> (located at the edge on the antenna) should be pointed north.<br /> c. The antenna will likely need to be rotated. Loosen the spike clamps and rotate in the clockwise (tightening)<br /> direction.<br /> 12) Hook the receiver up to power.<br /> <br /> 13) Attach the antenna cable to receiver and antenna.<br /> <br /> ===Orienting the antenna to TRUE NORTH===<br /> Every antenna has a reference line or arrow that must be oriented toward TRUE NORTH. The reason for this is that the position actually measured by GPS is something called the ''antenna phase center'', which in general is not located on the axis of the antenna. So if you orient the antenna in some other direction, you introduce an error into the resulting postion that for many antennas is much larger than the measurement uncertainty.<br /> :The reference arrow for the Trimble 4000's antenna is marked on the antenna.<br /> :For other antennas, the antenna cable connector should point to NORTH. There will normally be something marked on the top of the antenna along that same line.<br /> <br /> To orient the antenna, you need to know the magnetic declination. It should be recorded on the site description. If not, it can be found on any USGS topo map. If all else fails, remember 25 degrees east, which is not too far off for most of central and southern Alaska.<br /> :If the declination is EAST, set your compass to 360 - declination and orient by the north arrow on the compass.<br /> :If the declination is WEST, set your compass to 360 + declination and orient by the north arrow on the compass.<br /> <br /> If you find that you oriented the antenna the wrong way, and it is already recording data, don't do anything rash! The best thing to do in this case is to carefully record the actual orientation of the antenna. <br /> <br /> ===Programming a Trimble 4000 receiver===<br /> You can find a printable description of a [http://www.gps.alaska.edu/tfour/Misc/ReceiverSetup_multiday.pdf multi-day receiver setup] by clicking on that link.<br /> <br /> ===Using the Trimble 5700 and R7 receivers===<br /> These two receivers are basically the same thing. Neither one is convenient to program in the field. Turn them on and they should work.<br /> <br /> What the lights mean.<br /> <br /> <br /> ===Using the Trimble Net-RS receiver===<br /> <br /> The main issue with the Net-RS receiver is that it writes all data for one UTC day into ONE file. This must be<br /> considered when a station is moved within one UTC day between sites. It is possible to untangle the data but still it's a hassle. In Alaska a new UTC day starts at 4:00 pm, meaning that taking the station down before 4 pm and setting it out somewhere else after 4 pm would be ideal.<br /> <br /> If you must visit 2 sites on the same Julian day, here is a way to get the data to go into separate files. You'll need a laptop, and a crossover (Xover) ethernet cable. Set your network settings on the laptop to IP: 192.168.1.3 NetMask: 255.255.255.0 Gateway: 192.168.1.1<br /> Connect the laptop to the NetRS. Open internet explorer or equiv. and go to the site 192.168.1.2<br /> The web interface should appear with a blue background. Under Data Logging, switch from one 30sec 24hour session to another by toggling the appropriate "enable" boxes. If you need to program a second campaign session, read the manual.<br /> <br /> ATTN: The Net-RS receiver has different power and antenna inputs! Make sure you have the right cables (usually they do not fit into the black case) before you leave the vehicle, especially when the site is away from the road.<br /> <br /> ===Using the Topcon GB-1000 receiver===<br /> There is printable introduction here: [http://gps.alaska.edu/~yuning/topcongb1000.pdf Topcon Guide]<br /> <br /> <br /> ===Using the Topcon RTK setup ===<br /> This deserves its own site [[Topcon RTK]]<br /> <br /> ===Downloading the Trimble 4000 receiver===<br /> <br /> 1. Get DOS Laptop<br /> <br /> 2. Boot and cd to C:\DOWNLOAD<br /> <br /> 3. Connect Serial Cable (Port I/0 1)<br /> <br /> 4. Connect power (either 12V car battery or adapter)<br /> <br /> 5. start program '4000': <code>C:\DOWNLOAD>4000</code><br /> <br /> 6. rename files according to Julian day<br /> <br /> 7. follow screen instructions (make sure connection rate is the same as in receiver)<br /> <br /> 8. get data on memory card<br /> <br /> 9. ftp data from memory card that should be pushed into a different computer to linux system<br /> <br /> ===Downloading the Trimble 5700 receiver===<br /> <br /> We will use the "Windows system" computer to download data from Trimber 5700 receiver. And also make sure that log sheet is at your hand.<br /> <br /> 1. Take the Trimble 5700 receiver out from the yellow box (I know it's "crap", but it's exact what we do first).<br /> <br /> 2. There are two cables needed to plug into the receiver: power cable (circle); data cable (a little bit rectangular). Power on the receiver.<br /> <br /> 3. Double click "Shortcut to DataXfer.exe" on the computer desktop. If the receiver is already connected, the software will display the receiver and its series number, check the number and what was recorded on the log sheet, make sure they are matched.<br /> <br /> 4. Click the "add" button, then you can see all the recorded data in the receiver. Choose the data you want to download, and make sure save the data file to directory E:\GPSdata\. For example, if we want to download compaign data of KENAI trip in 2008, the subdirectory can be created as E:\GPSdata\data 2008\campaign\kenai, and the downloaded data should go to there. Then, click "Transfer", then you will see the computer doing its work to download data. And you need to click "OK" during the download.<br /> <br /> 5. Change files name. Usually, there are two files for one day of one site: *.dat and *.T00. Change the first 4 letters to site name for both of these two files. For example, for site DAHL, the data file name should be changed to the format like this: "dahl1430.dat" and "dahl1430.T00" (143 is the Julian day). If the name of site has only 3 letters (site CPR, for example), then names should be like this: "cpr_1450.dat" and "cpr_1450.T01". <br /> <br /> 6. The download work is done. Power off receiver and put the receiver back to the yellow box. Check if all the stuff (receiver, antenna, power cable, data cable) is the box before you close it.<br /> <br /> Then you can go on downloading next receiver. You can re-start the software (Shortcut to DataXfer.exe), then it will detect the new receiver automatically.<br /> <br /> ===Downloading the Trimble Net-RS receiver===<br /> [TODO.]<br /> <br /> ===What goes on the data log sheet?===<br /> Data log sheets are used to record important information regarding the site/benchmark and the survey session. We record information about the site, such as the name, benchmark inscription, and location. It is important to log information about the equipment used; including serial numbers, and type of equipment. We record hieght information, direction, as well as time and duration of the survey. It is important to log who conducted the survey as well as any unusual things/mishaps that occured during the survey. Follow the link to a printable [http://www.gps.alaska.edu/tfour/Misc/Alaska_Log.pdf log sheet].<br /> <br /> ===Where do data log sheets go===<br /> In the filing cabinet, in a hanging file stored by GPS campaign.<br /> <br /> Every year, we send a copy of all log sheets to [http://www.unavco.org UNAVCO] for permanent archiving, along with the data files. Sometimes after a while it is easier to find the information from the [http://www.unavco.org/facility/data/data.html UNAVCO Data Archive] than it is to find our own log sheets in the filing cabinet.<br /> <br /> <br /> ===Converting files to RINEX===<br /> The final step in the fieldwork is to convert the data files to the RINEX format. RINEX stands for '''R'''eceiver '''IN'''dependent '''EX'''change format. It is an ASCII format that is publicly documented and agreed upon worldwide. In contrast, the Trimble .dat and .t00/.t01 files are proprietary formats that are only used by Trimble. Naturally, every receiver manufacturer has its own proprietary format. There is a more compact binary format called BINEX that is meant to store the same information. BINEX has been adopted as the standard format for [http://pbo.unavco.org PBO], and may one day become the standard instead of RINEX.<br /> <br /> There are enough steps in the process that [[RINEXing|a complete guide]] is on its own page.<br /> <br /> <br /> ===Field Notes===<br /> [[Field Notes]] on successful and not-so-successful field excursions may help you plan your next trip.</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Subnets_GoogleEarth&diff=1943 Subnets GoogleEarth 2011-03-27T23:13:28Z

<p>Yuning: </p> <hr /> <div>The ".kml" files have been edit for ''Google Earth'', then you can "open" these files with ''Goolge Earth'' and play around with them.<br /> <br /> Download ".kml" files here:<br /> <br /> Alaska: <br /> <br /> [http://gps.alaska.edu/~yuning/subnets/Alaska.kml "Alaska.kml"]<br /> <br /> [http://gps.alaska.edu/~yuning/subnets/Alaska.jpg "Alaska.jpg"]<br /> <br /> CASA: <br /> <br /> [http://gps.alaska.edu/~yuning/subnets/CASA.kml "CASA.kml"]<br /> <br /> [http://gps.alaska.edu/~yuning/subnets/CASA.jpg "CASA.jpg"]<br /> <br /> EurAf: <br /> <br /> [http://gps.alaska.edu/~yuning/subnets/EurAf.kml "EurAf.kml"]<br /> <br /> [http://gps.alaska.edu/~yuning/subnets/EurAf.jpg "EurAf.jpg"]<br /> <br /> Greenland: <br /> <br /> [http://gps.alaska.edu/~yuning/subnets/Greenland.kml "Greenland.kml"]<br /> <br /> [http://gps.alaska.edu/~yuning/subnets/Greenland.jpg "Greenland.jpg"]<br /> <br /> NCal: <br /> <br /> [http://gps.alaska.edu/~yuning/subnets/NCal.kml "NCal.kml"]<br /> <br /> [http://gps.alaska.edu/~yuning/subnets/NCal.jpg "NCal.jpg"]<br /> <br /> NEAsia: <br /> <br /> [http://gps.alaska.edu/~yuning/subnets/NEAsia.kml "NEAsia.kml"]<br /> <br /> [http://gps.alaska.edu/~yuning/subnets/NEAsia.jpg "NEAsia.jpg"]<br /> <br /> NOAM: <br /> <br /> [http://gps.alaska.edu/~yuning/subnets/NOAM.kml "NOAM.kml"]<br /> <br /> [http://gps.alaska.edu/~yuning/subnets/NOAM.jpg "NOAM.jpg"]<br /> <br /> Tibet: <br /> <br /> [http://gps.alaska.edu/~yuning/subnets/Tibet.kml "Tibet.kml"]<br /> <br /> [http://gps.alaska.edu/~yuning/subnets/Tibet.jpg "Tibet.jpg"]<br /> <br /> TIGAswp: <br /> <br /> [http://gps.alaska.edu/~yuning/subnets/TIGAswp.kml "TIGAswp.kml"]<br /> <br /> [http://gps.alaska.edu/~yuning/subnets/TIGAswp.jpg "TIGAswp.jpg"]<br /> <br /> GEONET: <br /> <br /> [http://gps.alaska.edu/~yuning/subnets/GEONET.kml "GEONET.kml"]<br /> <br /> [http://gps.alaska.edu/~yuning/subnets/GEONET.jpg "GEONET.jpg"]</div>

Yuning http://gps.alaska.edu/internal/index.php?title=To_do_list&diff=1940 To do list 2010-09-04T02:35:30Z

<p>Yuning: /* All New Students */</p> <hr /> <div>__TOC__<br /> === All New Students ===<br /> Welcome in Alaska, Fairbanks, at the Geophysical Institute (GI), Geodesy Lab!<br /> <br /> This brief list should give you some points to start with. If you encounter difficulties, ask questions, contact people, ... <br /> <br /> It is not unusual, that people use abbreviations, which you might not be familiar with, especially if you are not American. So follow the link [[abbreviations]], where we listed a few of them. And again, ask, if you do not understand what people are talking about.<br /> <br /> <br /> <br /> '''meet Jeff'''<br><br /> His office is in the Elvey Building, room 413B (4th floor in the GI). Phone: (907) 474-7286<br /> <br /> '''expect lots of paperwork'''<br><br /> ... especially when you are an international student. Also expect that most of this must be done every semester so you might want to keep a list :)<br /> <br /> '''get username and password''' (e.g. for GI webpage/account)<br><br /> Jeff will introduce you to Dave Covey (-5913) and/or Paul Delys (-7418) at CRC, who can help you also with about any computer and/or software problem you might have. http://www.gi.alaska.edu/crc/<br /> <br /> '''visit human resources and payroll office'''<br><br /> These offices are located on the 6th floor in the GI. Expect, that you have to do a lot of paperwork. If you are an RA/TA (Research Assistant / Teaching Assistant) make sure you get the letter telling the GI offers you this. http://www.gi.alaska.edu/admin/human_resources/<br /> <br /> '''timesheets'''<br><br /> You need to fill out timesheets in order to get payed. Therefore it is necessary that<br> <br /> (1<sup>st</sup>) the timesheet-link is present on your account page (https://patch.gi.alaska.edu/index.php) (automatically updated every Monday) and<br><br /> (2<sup>nd</sup>) you fill it out, have it signed by your supervisor (i.e., Jeff), and submit it to payroll (6th floor, HR office).<br /> <br /> Help to set up that tool will be through CRC (for (1)) and payroll itself (for(2)).<br /> <br /> '''Graduate School'''<br><br /> If you are a gratuate student, you will need to see the Graduate School staff in order to e.g. register for classes, get health insurance ... . http://www.uaf.edu/gradsch/<br /> <br /> There is a catalog (studying guide) which includes information about academic issues at UAF in general and the requirements of any/your degree program specifically. You can get that catalog at many places e.g. the library, Graduate School, ... and online at http://www.uaf.edu/catalog/<br><br /> Make sure to keep a copy of the catalog under which you entered UAF. It is the one that is effectual for all your time here (catalogs tend to change anually).<br /> <br /> '''health insurence'''<br><br /> Make sure you have it, either through UAF/GI or private.<br /> <br /> '''live'''<br><br /> If you want to live on compus, Cutler Apartment is a good choice. Because it is near to GI building, and you can cook by yourself there.<br /> http://www.uaf.edu/reslife/campus.htm<br /> <br /> '''get keys'''<br><br /> You can get keys both for GI entrance doors and the Lab door at the Operations Office, located in Rm. 616 Elvey (6th floor in the GI, Jeff will need to sign and will probably take you there).<br /> <br /> '''apply "DuoProx Card" for GI library'''<br><br /> 1. Get the application form from GI library (second floor in Int'l Arctic Research Center)<br /> 2. Get signature from Jeff.<br /> 3. Back to GI library to get the card.<br /> <br /> '''register for classes'''<br><br /> http://www.alaska.edu/uaf/coursefinder/<br /> If you want to change your courses selection, please let the officer of graduate shool know, and they will help to deal with tuition change.<br /> <br /> '''Department of Geology and Geophysics'''<br><br /> This department is located in the Reichardt Building, Room 308. If not allready, you will hear about that office and staff and you might need to indroduce yourself to them. http://www.uaf.edu/geology/<br /> <br /> '''meetings'''<br><br /> Ask about regular scheduled meetings (e.g. AVO meeting, Friday Seminar).<br /> <br /> '''orientation'''<br><br /> Make sure you know what that is. If it is required for you (certainly for International Students, at least parts are mandatory for everyone, e.g. Grad School Orientation ... which helps a lot), make sure that you are registered and attend it.<br /> <br /> '''Get an AK driver's license'''<br><br /> For some reason this must be done in the first 90 days of your stay. Otherwise, it is said, you will not get one.<br /> <br /> === International Students ===<br /> <br /> '''see the International Student Advisor(s) at the Office of International Programs'''<br><br /> http://www.uaf.edu/oip<br /> <br /> <br /> <br /> === Abbreviations ===<br /> '''GI''' Geophysical Institute (located in the Elvey Building)<br><br /> '''HR''' human resources</div>

Yuning http://gps.alaska.edu/internal/index.php?title=To_do_list&diff=1939 To do list 2010-09-04T02:34:45Z

<p>Yuning: /* All New Students */</p> <hr /> <div>__TOC__<br /> === All New Students ===<br /> Welcome in Alaska, Fairbanks, at the Geophysical Institute (GI), Geodesy Lab!<br /> <br /> This brief list should give you some points to start with. If you encounter difficulties, ask questions, contact people, ... <br /> <br /> It is not unusual, that people use abbreviations, which you might not be familiar with, especially if you are not American. So follow the link [[abbreviations]], where we listed a few of them. And again, ask, if you do not understand what people are talking about.<br /> <br /> <br /> <br /> '''meet Jeff'''<br><br /> His office is in the Elvey Building, room 413B (4th floor in the GI). Phone: (907) 474-7286<br /> <br /> '''expect lots of paperwork'''<br><br /> ... especially when you are an international student. Also expect that most of this must be done every semester so you might want to keep a list :)<br /> <br /> '''get username and password''' (e.g. for GI webpage/account)<br><br /> Jeff will introduce you to Dave Covey (-5913) and/or Paul Delys (-7418) at CRC, who can help you also with about any computer and/or software problem you might have. http://www.gi.alaska.edu/crc/<br /> <br /> '''visit human resources and payroll office'''<br><br /> These offices are located on the 6th floor in the GI. Expect, that you have to do a lot of paperwork. If you are an RA/TA (Research Assistant / Teaching Assistant) make sure you get the letter telling the GI offers you this. http://www.gi.alaska.edu/admin/human_resources/<br /> <br /> '''timesheets'''<br><br /> You need to fill out timesheets in order to get payed. Therefore it is necessary that<br> <br /> (1<sup>st</sup>) the timesheet-link is present on your account page (https://patch.gi.alaska.edu/index.php) (automatically updated every Monday) and<br><br /> (2<sup>nd</sup>) you fill it out, have it signed by your supervisor (i.e., Jeff), and submit it to payroll (6th floor, HR office).<br /> <br /> Help to set up that tool will be through CRC (for (1)) and payroll itself (for(2)).<br /> <br /> '''Graduate School'''<br><br /> If you are a gratuate student, you will need to see the Graduate School staff in order to e.g. register for classes, get health insurance ... . http://www.uaf.edu/gradsch/<br /> <br /> There is a catalog (studying guide) which includes information about academic issues at UAF in general and the requirements of any/your degree program specifically. You can get that catalog at many places e.g. the library, Graduate School, ... and online at http://www.uaf.edu/catalog/<br><br /> Make sure to keep a copy of the catalog under which you entered UAF. It is the one that is effectual for all your time here (catalogs tend to change anually).<br /> <br /> '''health insurence'''<br><br /> Make sure you have it, either through UAF/GI or private.<br /> <br /> '''live'''<br><br /> If you want to live on compus, Cutler Apartment is a good choice. Because it is near to GI building, and you can cook by yourself there.<br /> http://www.uaf.edu/reslife/campus.htm<br /> <br /> '''get keys'''<br><br /> You can get keys both for GI entrance doors and the Lab door at the Operations Office, located in Rm. 616 Elvey (6th floor in the GI, Jeff will need to sign and will probably take you there).<br /> <br /> '''apply "DuoProx Card" for GI library'''<br><br /> 1. Get the application form from GI library (second floor in Int'l Arctic Research)<br /> 2. Get signature from Jeff.<br /> 3. Back to GI library to get the card.<br /> <br /> '''register for classes'''<br><br /> http://www.alaska.edu/uaf/coursefinder/<br /> If you want to change your courses selection, please let the officer of graduate shool know, and they will help to deal with tuition change.<br /> <br /> '''Department of Geology and Geophysics'''<br><br /> This department is located in the Reichardt Building, Room 308. If not allready, you will hear about that office and staff and you might need to indroduce yourself to them. http://www.uaf.edu/geology/<br /> <br /> '''meetings'''<br><br /> Ask about regular scheduled meetings (e.g. AVO meeting, Friday Seminar).<br /> <br /> '''orientation'''<br><br /> Make sure you know what that is. If it is required for you (certainly for International Students, at least parts are mandatory for everyone, e.g. Grad School Orientation ... which helps a lot), make sure that you are registered and attend it.<br /> <br /> '''Get an AK driver's license'''<br><br /> For some reason this must be done in the first 90 days of your stay. Otherwise, it is said, you will not get one.<br /> <br /> === International Students ===<br /> <br /> '''see the International Student Advisor(s) at the Office of International Programs'''<br><br /> http://www.uaf.edu/oip<br /> <br /> <br /> <br /> === Abbreviations ===<br /> '''GI''' Geophysical Institute (located in the Elvey Building)<br><br /> '''HR''' human resources</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Fieldwork&diff=1690 Fieldwork 2009-08-11T00:48:48Z

<p>Yuning: </p> <hr /> <div>:''Reach site, hunt around,''<br /> :''Setup, precise centering,''<br /> :''Yellow box takes data.''<br /> ::''- A concise guide to GPS fieldwork''<br /> <br /> Perhaps the most important thing to remember about GPS fieldwork is that with a 24-hour GPS survey you can measure the position of the GPS antenna to within about 2 mm horizontal precision and 6 mm vertical precision, and you can measure the vector between two GPS antennas even more precisely than that. What this means is that the tolerances for setup error are very tight and you have to be very careful. If not, YOU are likely to be the limiting error source in the measurements. It also means that you really can't hide it if you screw up. So do your best if you make a mistake or something odd happens, carefully record it on the log sheet. It is far better to know we have a bad observation than to find out years later.<br /> <br /> ===Where can I find site information?===<br /> We maintain a [http://gps.alaska.edu/gps GPS Site Database] that in theory stores site information from all the GPS sites we use. In practice, some are missing, but the database is mostly complete for Alaska and environs. You can search the database by 4 characeter ID, or radial or rectangular searches, and other ways as well. To access the database, you need a login and password, and for that you need to ask Jeff.<br /> <br /> ===Where to find Julian Day Calendar===<br /> Here is printable Julian Day Calendar: [http://gps.alaska.edu/~yuning/JulianDayCalendar.pdf Julian Day]<br /> <br /> ===Traveling in Alaska===<br /> <br /> Before you go on official University travel be sure to fill out a Travel Authorization (TA) form. You can get this from Candice Lake on the 6th floor in the buisness office. Even if you do not expect to spend money on the trip, it is important that you fill out this form for insurance purposes. When you return it is necessary to fill out an expense report (to be sure you are reimbursed for incurred costs), even if you had no expenses.<br /> <br /> <b>Rental Cars</b><br><br /> A rental is often the cheapest way to travel on the road network in Alaska. If you are traveling on University buisness (fieldwork falls in this <br /> category) then the university covers the insurance, be sure to decline coverage when renting the car. Be sure to print [http://gps.alaska.edu/tfour/Misc/travel_papers.pdf this document] when traveling in a rental car; it contains [http://gps.alaska.edu/tfour/Misc/travel_papers.pdf proof of insurance] and some phone numbers to call if an accident occurs. The GI recommends that you '''not''' rent from Budget due to their aggressive collection agency should damages occur to the vehicle while in your possesion. The GI recommends using [http://www.avis.com Avis] or some other rental company. Do not rent from the airport rental location, there is an additional 10% tax plus fees added to the price of rental if you rent from the airport. Most of the rental companies have other locations in town, which have lower costs. <br /> <br /> <b>Flying in the Bush</b><br><br /> This is not your regular commercial flight, get all the information you need prior to departure.<br /> <br /> <br /> ===How to set up a tripod===<br /> <br /> There are as many different explanations as people who have set up a tripod before. Well, one description you can use is this: Follow the link to a printable [http://www.gps.alaska.edu/tfour/Misc/tripodsetup1.pdf setup description] and/or the link to [[new site and tripod setup description]].<br /> <br /> ===How to set up a spike mount===<br /> 1) Locate benchmark with hand-held GPS or site description.<br /> <br /> 2) Assemble spike mount by attaching legs to spike.<br /> a. *Out of the case the legs on the spike mount will be short. Use the leg extensions as needed to improve stability.<br /> b. Additional wing-nuts, lock washers and spike tips are included in the case<br /> 3) Set the spike on the benchmark with the legs oriented at 90 degrees from each other, or as close to 90 as possible.<br /> <br /> 4) Loosely tighten the wing-nut on the leg extensions to hold the leg lengths.<br /> <br /> 5) Use the carpenter’s level and the leg screws to level each leg independently.<br /> <br /> 6) Loosen the wing nuts and add weights (rocks) to hold the leg positions, retighten the wing nuts.<br /> <br /> 7) Attach the leveling plate to the spike and place the bull’s-eye level on the plate.<br /> <br /> 8) Use the leg screw to level the plate. Once the plate is level tighten the locking nut on the legs.<br /> <br /> 9) Remove the leveling plate.<br /> <br /> 10) Attach the antenna to the spike. ** Do not attach the antenna cable yet.**<br /> a. Make sure at least one spike clamp is tight, to ensure that the spike doesn’t rotate when tightening the antenna.<br /> 11) Orient the antenna to north.<br /> a. Set the declination on your compass, the compass can be placed directly onto the antenna. <br /> b. Some antennas are marked with a North arrow others are not. If there is no North direction indicated, Notch 1 <br /> (located at the edge on the antenna) should be pointed north.<br /> c. The antenna will likely need to be rotated. Loosen the spike clamps and rotate in the clockwise (tightening)<br /> direction.<br /> 12) Hook the receiver up to power.<br /> <br /> 13) Attach the antenna cable to receiver and antenna.<br /> <br /> ===Orienting the antenna to TRUE NORTH===<br /> Every antenna has a reference line or arrow that must be oriented toward TRUE NORTH. The reason for this is that the position actually measured by GPS is something called the ''antenna phase center'', which in general is not located on the axis of the antenna. So if you orient the antenna in some other direction, you introduce an error into the resulting postion that for many antennas is much larger than the measurement uncertainty.<br /> :The reference arrow for the Trimble 4000's antenna is marked on the antenna.<br /> :For other antennas, the antenna cable connector should point to NORTH. There will normally be something marked on the top of the antenna along that same line.<br /> <br /> To orient the antenna, you need to know the magnetic declination. It should be recorded on the site description. If not, it can be found on any USGS topo map. If all else fails, remember 25 degrees east, which is not too far off for most of central and southern Alaska.<br /> :If the declination is EAST, set your compass to 360 - declination and orient by the north arrow on the compass.<br /> :If the declination is WEST, set your compass to 360 + declination and orient by the north arrow on the compass.<br /> <br /> If you find that you oriented the antenna the wrong way, and it is already recording data, don't do anything rash! The best thing to do in this case is to carefully record the actual orientation of the antenna. <br /> <br /> ===Programming a Trimble 4000 receiver===<br /> You can find a printable description of a [http://www.gps.alaska.edu/tfour/Misc/ReceiverSetup_multiday.pdf multi-day receiver setup] by clicking on that link.<br /> <br /> ===Using the Trimble 5700 and R7 receivers===<br /> These two receivers are basically the same thing. Neither one is convenient to program in the field. Turn them on and they should work.<br /> <br /> What the lights mean.<br /> <br /> <br /> ===Using the Trimble Net-RS receiver===<br /> <br /> The main issue with the Net-RS receiver is that it writes all data for one UTC day into ONE file. This must be<br /> considered when a station is moved within one UTC day between sites. It is possible to untangle the data but still it's a hassle. In Alaska a new UTC day starts at 4:00 pm, meaning that taking the station down before 4 pm and setting it out somewhere else after 4 pm would be ideal.<br /> <br /> If you must visit 2 sites on the same Julian day, here is a way to get the data to go into separate files. You'll need a laptop, and a crossover (Xover) ethernet cable. Set your network settings on the laptop to IP: 192.168.1.3 NetMask: 255.255.255.0 Gateway: 192.168.1.1<br /> Connect the laptop to the NetRS. Open internet explorer or equiv. and go to the site 192.168.1.2<br /> The web interface should appear with a blue background. Under Data Logging, switch from one 30sec 24hour session to another by toggling the appropriate "enable" boxes. If you need to program a second campaign session, read the manual.<br /> <br /> ATTN: The Net-RS receiver has different power and antenna inputs! Make sure you have the right cables (usually they do not fit into the black case) before you leave the vehicle, especially when the site is away from the road.<br /> <br /> ===Using the Topcon GB-1000 receiver===<br /> There is printable introduction here: [http://gps.alaska.edu/~yuning/topcongb1000.pdf Topcon Guide]<br /> <br /> ===Downloading the Trimble 4000 receiver===<br /> <br /> 1. Get DOS Laptop<br /> <br /> 2. Boot and cd to C:\DOWNLOAD<br /> <br /> 3. Connect Serial Cable (Port I/0 1)<br /> <br /> 4. Connect power (either 12V car battery or adapter)<br /> <br /> 5. start program '4000': <code>C:\DOWNLOAD>4000</code><br /> <br /> 6. rename files according to Julian day<br /> <br /> 7. follow screen instructions (make sure connection rate is the same as in receiver)<br /> <br /> 8. get data on memory card<br /> <br /> 9. ftp data from memory card that should be pushed into a different computer to linux system<br /> <br /> ===Downloading the Trimble 5700 receiver===<br /> <br /> We will use the "Windows system" computer to download data from Trimber 5700 receiver. And also make sure that log sheet is at your hand.<br /> <br /> 1. Take the Trimble 5700 receiver out from the yellow box (I know it's "crap", but it's exact what we do first).<br /> <br /> 2. There are two cables needed to plug into the receiver: power cable (circle); data cable (a little bit rectangular). Power on the receiver.<br /> <br /> 3. Double click "Shortcut to DataXfer.exe" on the computer desktop. If the receiver is already connected, the software will display the receiver and its series number, check the number and what was recorded on the log sheet, make sure they are matched.<br /> <br /> 4. Click the "add" button, then you can see all the recorded data in the receiver. Choose the data you want to download, and make sure save the data file to directory E:\GPSdata\. For example, if we want to download compaign data of KENAI trip in 2008, the subdirectory can be created as E:\GPSdata\data 2008\campaign\kenai, and the downloaded data should go to there. Then, click "Transfer", then you will see the computer doing its work to download data. And you need to click "OK" during the download.<br /> <br /> 5. Change files name. Usually, there are two files for one day of one site: *.dat and *.T00. Change the first 4 letters to site name for both of these two files. For example, for site DAHL, the data file name should be changed to the format like this: "dahl1430.dat" and "dahl1430.T00" (143 is the Julian day). If the name of site has only 3 letters (site CPR, for example), then names should be like this: "cpr_1450.dat" and "cpr_1450.T01". <br /> <br /> 6. The download work is done. Power off receiver and put the receiver back to the yellow box. Check if all the stuff (receiver, antenna, power cable, data cable) is the box before you close it.<br /> <br /> Then you can go on downloading next receiver. You can re-start the software (Shortcut to DataXfer.exe), then it will detect the new receiver automatically.<br /> <br /> ===Downloading the Trimble Net-RS receiver===<br /> <br /> <br /> ===What goes on the data log sheet?===<br /> Data log sheets are used to record important information regarding the site/benchmark and the survey session. We record information about the site, such as the name, benchmark inscription, and location. It is important to log information about the equipment used; including serial numbers, and type of equipment. We record hieght information, direction, as well as time and duration of the survey. It is important to log who conducted the survey as well as any unusual things/mishaps that occured during the survey. Follow the link to a printable [http://www.gps.alaska.edu/tfour/Misc/Alaska_Log.pdf log sheet].<br /> <br /> ===Where do data log sheets go===<br /> In the filing cabinet, in a hanging file stored by GPS campaign.<br /> <br /> Every year, we send a copy of all log sheets to [http://www.unavco.org UNAVCO] for permanent archiving, along with the data files. Sometimes after a while it is easier to find the information from the [http://www.unavco.org/facility/data/data.html UNAVCO Data Archive] than it is to find our own log sheets in the filing cabinet.<br /> <br /> <br /> ===Converting files to RINEX===<br /> The final step in the fieldwork is to convert the data files to the RINEX format. RINEX stands for '''R'''eceiver '''IN'''dependent '''EX'''change format. It is an ASCII format that is publicly documented and agreed upon worldwide. In contrast, the Trimble .dat and .t00/.t01 files are proprietary formats that are only used by Trimble. Naturally, every receiver manufacturer has its own proprietary format. There is a more compact binary format called BINEX that is meant to store the same information. BINEX has been adopted as the standard format for [http://pbo.unavco.org PBO], and may one day become the standard instead of RINEX.<br /> <br /> There are enough steps in the process that [[RINEXing|a complete guide]] is on its own page.<br /> <br /> <br /> ===Field Notes===<br /> [[Field Notes]] on successful and not-so-successful field excursions may help you plan your next trip.</div>

Yuning http://gps.alaska.edu/internal/index.php?title=RoiPac&diff=1603 RoiPac 2008-09-17T17:43:06Z

<p>Yuning: /* ROI_PAC */</p> <hr /> <div>Our lab has installed ROI_PAC 3.0 for SAR and InSAR processing. Some detailed introductions and explainations will be followed soon. And also, you can get information about InSAR and ROI_PAC from the links below.<br /> <br /> http://roipac.org/<br /> <br /> http://www.uoregon.edu/~das/WikiRoiPac/doku.php?id=welcome<br /> <br /> === ROI_PAC (3.0)===<br /> <br /> ROI_PAC is located at /usr/local/ROI_PAC_3_0/ROI_PAC, and there is also SAR data available for your test at /usr/local/TEST_DIR directory. More information about how to play with it will be updated soon.<br /> <br /> ===Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC.===<br /> <br /> Take the test data (/usr/local/TEST_DIR) for example to explain the processing.<br /> <br /> First, compile some environment variable and path used by ROI_PCA. There is already a template file named SAR_CONFIG at /usr/local/ROI_PAC_3_0/ROI_PAC. Change the necessary commands, and then "source" it.<br /> <br /> source SAR_CONFIG<br /> <br /> <br /> Then, ingest the data. Go to the SAR data directory (/usr/local/TEST_DIR/930110 and /usr/local/TEST_DIR/950523), and ingest data respectively. <br /> <br /> TEST_DIR/930110> make_raw.pl PRC SARLEADER1993011018252739T1Of1 930110 <br /> TEST_DIR/950523> make_raw.pl PRC SARLEADER1995052318253409T1Of1 950523 <br /> <br /> Note: Different SAR data format has different command to ingest. For our case, they are ERS data, so "make_raw.pl" is used.<br /> <br /> Last, data processing. Actually, there is a command "process_2pass.pl" can run all the steps after raw data ready. And the file "int.proc" in main directory (/usr/local/TEST_DIR) specifiles two scene directories (data and orbit) and other processing parameters for a given interferogram.<br /> <br /> process_2pass.pl int.proc<br /> <br /> And also, we can do it step by step.<br /> <br /> process_2pass.pl int.proc [DoItFrom EndItAt]<br /> <br /> DoItFrom = point in process.pl to start<br /> EndItAt = point in process.pl to end<br /> Can be: raw, roi_prep, orbbase, slcs, offsets, resamp, flatorb, full_res, filtered, make_mask, unwrapped, simulation, morph_sim, <br /> redo_base or use_sim_base<br /> EndItAt can also be synth_offset<br /> <br /> For more information about ROI_PAC, please refer POI_PAC [http://roipac.org/ website] and Eric Fielding's ppt [http://gps.alaska.edu/~yuning/Eric_Roipac.ppt "ROI-pac Internals"].<br /> <br /> And also, you can look at Andrew Newman's introduction for ROI_PAC processing here:<br /> http://geophysics.eas.gatech.edu/people/anewman/classes/MGM/InSAR/Setup.html</div>

Yuning http://gps.alaska.edu/internal/index.php?title=RoiPac&diff=1602 RoiPac 2008-09-17T17:42:42Z

<p>Yuning: /* ROI_PAC */</p> <hr /> <div>Our lab has installed ROI_PAC 3.0 for SAR and InSAR processing. Some detailed introductions and explainations will be followed soon. And also, you can get information about InSAR and ROI_PAC from the links below.<br /> <br /> http://roipac.org/<br /> <br /> http://www.uoregon.edu/~das/WikiRoiPac/doku.php?id=welcome<br /> <br /> === ROI_PAC ===<br /> <br /> ROI_PAC is located at /usr/local/ROI_PAC_3_0/ROI_PAC, and there is also SAR data available for your test at /usr/local/TEST_DIR directory. More information about how to play with it will be updated soon.<br /> <br /> ===Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC.===<br /> <br /> Take the test data (/usr/local/TEST_DIR) for example to explain the processing.<br /> <br /> First, compile some environment variable and path used by ROI_PCA. There is already a template file named SAR_CONFIG at /usr/local/ROI_PAC_3_0/ROI_PAC. Change the necessary commands, and then "source" it.<br /> <br /> source SAR_CONFIG<br /> <br /> <br /> Then, ingest the data. Go to the SAR data directory (/usr/local/TEST_DIR/930110 and /usr/local/TEST_DIR/950523), and ingest data respectively. <br /> <br /> TEST_DIR/930110> make_raw.pl PRC SARLEADER1993011018252739T1Of1 930110 <br /> TEST_DIR/950523> make_raw.pl PRC SARLEADER1995052318253409T1Of1 950523 <br /> <br /> Note: Different SAR data format has different command to ingest. For our case, they are ERS data, so "make_raw.pl" is used.<br /> <br /> Last, data processing. Actually, there is a command "process_2pass.pl" can run all the steps after raw data ready. And the file "int.proc" in main directory (/usr/local/TEST_DIR) specifiles two scene directories (data and orbit) and other processing parameters for a given interferogram.<br /> <br /> process_2pass.pl int.proc<br /> <br /> And also, we can do it step by step.<br /> <br /> process_2pass.pl int.proc [DoItFrom EndItAt]<br /> <br /> DoItFrom = point in process.pl to start<br /> EndItAt = point in process.pl to end<br /> Can be: raw, roi_prep, orbbase, slcs, offsets, resamp, flatorb, full_res, filtered, make_mask, unwrapped, simulation, morph_sim, <br /> redo_base or use_sim_base<br /> EndItAt can also be synth_offset<br /> <br /> For more information about ROI_PAC, please refer POI_PAC [http://roipac.org/ website] and Eric Fielding's ppt [http://gps.alaska.edu/~yuning/Eric_Roipac.ppt "ROI-pac Internals"].<br /> <br /> And also, you can look at Andrew Newman's introduction for ROI_PAC processing here:<br /> http://geophysics.eas.gatech.edu/people/anewman/classes/MGM/InSAR/Setup.html</div>

Yuning http://gps.alaska.edu/internal/index.php?title=WHOS&diff=1562 WHOS 2008-08-13T19:28:42Z

<p>Yuning: /* Week Schedule as of 9/7/07 */</p> <hr /> <div>The WHOS list tracks assigned GPS weeks for processing.<br /> <br /> More details about analysis at [[GPS analysis system]].<br /> <br /> ===Recent weeks===<br /> <pre><br /> week # start date last processed who status<br /> ****************************************************************<br /> 1375 05/14/2006 Trivikram/trivikram 1/ CLEAN EXCEPT 2 DAYS<br /> 1376 05/21/2006 Trivikram/1-2/ CLEAN<br /> 1377 05/28/2006 07/20/2006 Trivikram 1<br /> 1378 06/04/2006 07/20/2006 Trivikram 1 <br /> 1379 06/11/2006 07/20/2006 Trivikram 1 <br /> 1380 06/18/2006 07/20/2006 Trivikram 1 <br /> 1381 06/25/2006 07/12/2006 Ryan<br /> 1382 07/02/2006 Julie<br /> 1383 07/09/2006 Julie<br /> 1384 07/16/2006 Julie<br /> 1385 07/23/2006 Julie<br /> <br /> 1413 02/04/2007 05/01/2007 Tom<br /> </pre><br /> ===Week Schedule as of 9/7/07===<br /> <pre><br /> week # start date last processed who status<br /> *************************************************************<br /> 1430 Brandon NEAsia Alaska and NOAM-clean<br /> <br /> 1431 09/??/2007 10/31/2007 Lissy AK - clean<br /> 1431 11/05/2007 01/??/2008 Lissy initial cleaning done for Tibet solution<br /> 1431 01/09/2008 Lissy Casa solutions started<br /> <br /> 1432 Yuning initial cleaning done<br /> 1433 09/14/2007 09/26/2007 Ronni 1st iteration <br /> 1434 Julie<br /> 1435 Julie<br /> 1436 Julie<br /> 1437 Julie<br /> 1438 Julie<br /> 1439 Brandon one more iteration<br /> 1440 12?/??/2007 Lissy<br /> 1441 Yuning initial cleaning done<br /> 1442 09/27/2007 Ronni initial cleaning done<br /> 1443 Brandon NEA clean<br /> 1444 01/16/2008 Lissy<br /> 1445 Yuning initial cleaning done<br /> 1446 03/11/2008 Ronni<br /> 1447 Brandon initial cleaning done<br /> 1448 11/16/2007 05/12/2008 Lissy initial cleaning done<br /> 1449 Brandon NEA and Alaska cleaned<br /> 1450 Brandon initial cleaning done<br /> 1451 Brandon initial cleaning done<br /> 1452 01/23/2008 01/28/2008 Lissy initial cleaning done for Tibet & casa solution <br /> 1453 Yuning initial cleaning done<br /> 1454 05/05/2008 Ronni AK first interation<br /> 1455 Brandon initial cleaning done<br /> 1456 01/28/2008 Lissy<br /> 1457 Yuning initial cleaning done<br /> 1458 05/05/2008 Ronni AK first interation<br /> 1459 Julie<br /> 1460 Brandon NEA and AK cleaned<br /> 1461 02/06/2008 Lissy<br /> 1462 Yuning initial cleaning done<br /> 1463 05/05/2008 Ronni AK first interation<br /> 1464 Julie<br /> 1465 Brandon initial cleaning done<br /> 1466 04/09/2008 Lissy<br /> 1467 Yuning initial cleaning done<br /> 1468 05/05/2008 Ronni AK first interation<br /> 1469 Julie<br /> 1470 Brandon AK and NEA first iteration<br /> 1471 04/09/2008 Lissy<br /> 1472 Yuning initial cleaning done<br /> 1473 05/05/2008 Ronni AK first interation<br /> 1474 Julie<br /> 1475 Brandon AK first iteration<br /> 1476 Lissy<br /> 1477 Yuning AK cleaning done<br /> 1478 05/05/2008 Ronni AK first interation<br /> 1479 Julie<br /> 1480 Brandon<br /> 1481 Lissy<br /> 1482 Yuning<br /> 1483 Ronni<br /> 1484 Julie<br /> 1485 Brandon<br /> 1486 Lissy<br /> 1487 Yuning<br /> 1488 Ronni<br /> 1489 Julie<br /> 1490 Brandon<br /> 1491 Lissy<br /> 1492 Yuning<br /> 1493 Ronni<br /> 1494 Julie<br /> 1495 Brandon<br /> 1496 Lissy<br /> 1497 Yuning<br /> 1498 Ronni<br /> 1499 Julie<br /> 1500 Brandon<br /> <br /> </pre><br /> <br /> ===2006===<br /> <pre><br /> week # start date last processed who status<br /> ****************************************************************<br /> 1357 01/08/2006 Sandeep CLEANING Venkat<br /> 1358 01/15/2006 Sandeep CLEANING Venkat<br /> 1359 01/22/2006 Sandeep CLEAN Venkat (AK Point File Size < 300)<br /> 1360 01/29/2006 Sandeep CLEANING Venkat<br /> 1361 02/05/2006 Trivikram<br /> 1362 02/12/2006 Trivikram CLEAN (AK Point file size < 400)<br /> 1363 02/19/2006 Venkat CLEAN (AK Point file size < 400)<br /> 1364 02/26/2006 Trivikram<br /> 1365 03/05/2006 Venkat CLEANING <br /> 1366 03/12/2006 Trivikram<br /> 1367 03/19/2006 Trivikram <br /> 1368 03/26/2006 Trivikram problem with AK CLEANING SOLN<br /> 1369 04/02/2006 Trivikram CLEAN<br /> 1370 04/09/2006 Tom <br /> 1371 04/16/2006 Venkat CLEANING<br /> 1372 04/23/2006 Venkat CLEANING <br /> 1373 04/30/2006 Venkat CLEANING<br /> 1374 05/07/2006 Venkat CLEANING<br /> </pre><br /> <br /> ===2005===<br /> <pre><br /> week # start date last processed who status<br /> ****************************************************************<br /> 1304 01/02/2005 09/16/2005 Ryan CLEAN<br /> 1305 01/09/2005 08/30/2005 Pravee CLEAN<br /> 1306 01/16/2005 07/15/2005 Jill WORKING Trivikram(tibet) 07/26/2006 CLEAN<br /> 1307 01/23/2005 08/31/2005 Pravee CLEAN Trivikram(tibet) 07/26/2006 CLEAN<br /> 1308 01/30/2005 04/05/2005 Jill CLEAN Trivikram(tibet) 07/26/2006 CLEAN<br /> 1309 02/06/2005 08/31/2005 Pravee CLEAN <br /> 1310 02/13/2005 03/12/2005 Julie CLEAN <br /> 1311 02/20/2005 03/12/2005 Pravee CLEANING<br /> 1312 02/27/2005 03/31/2005 Tom CLEAN<br /> 1313 03/06/2005 03/31/2005 Pravee CLEANING<br /> 1314 03/13/2005 03/31/2005 Tom CLEAN<br /> 1315 03/20/2005 06/13/2005 Samik CLEAN (Point File Size < 500)<br /> 1316 03/27/2005 06/13/2005 Samik CLEAN (Point File Size < 400) <br /> 1317 04/03/2005 06/16/2005 Samik CLEAN (Point File Size < 400)<br /> 1318 04/10/2005 9/15/2005 Ryan not sure what's going on?<br /> 1319 04/17/2005 10/4/2005 Ryan ak SUBMITTED<br /> 1320 04/24/2005 Sandeep Done 1 2 Trivikram(tibet) 07/27/2006 1 2 CLEAN except 2 days<br /> 1321 05/01/2005 Sandeep Done 1 2 Trivikram(tibet) 07/28/2006 1 <br /> 1322 05/08/2005 Sandeep Done 1 2 Trivikram(tibet) 07/28/2006 1<br /> 1323 05/15/2005 Sandeep Done 1 2 Trivikram(tibet) 08/04/2006 1 <br /> 1324 05/22/2005 Sandeep Done 1 2 Trivikram(tibet) 08/04/2006 1<br /> 1325 05/29/2005 Sigrun DONE Trivikram(tibet) 08/04/2006 1<br /> 1326 06/05/2005 Sigrun DONE Trivikram(tibet) 08/06/2006 1<br /> 1327 06/12/2005 Sandeep Done 1 2 NO TIBET<br /> 1328 06/19/2005 Sandeep Done 1 2 No TIBET<br /> 1329 06/26/2005 Sandeep Done 1 2 Trivikram(tibet) 08/18/2006 1<br /> 1330 07/03/2005 9/14/2005 Ryan DONE<br /> 1331 07/10/2005 11/10/2005 Tom Submitted<br /> 1332 07/17/2005 Sandeep CLEAN Venkat (AK Point File Size < 500)<br /> 1333 07/24/2005 Sandeep CLEAN Trivikram <br /> 1334 07/31/2005 Sandeep CLEAN Trivikram <br /> 1335 08/07/2005 9/12/2005 Tom CLEAN Venkat (AK Point File Size < 400)<br /> 1336 08/14/2005 Sandeep CLEAN Venkat (AK Point File Size < 300)<br /> 1337 08/21/2005 10/17/2005 Ryan ak CLEAN Venkat (AK Point File Size < 300) <br /> 1338 08/28/2005 10/17/2005 Ryan ak CLEAN Venkat (AK Point File Size < 300) <br /> 1339 09/04/2005 11/08/2005 Ryan CLEAN Trivikram (AK Point File Size < 300) <br /> 1340 09/11/2005 Sandeep CLEAN Venkat (AK Point File Size < 300)<br /> 1341 09/18/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1342 09/25/2005 Sandeep CLEAN Venkat (AK Point File Size < 300) <br /> 1343 10/02/2005 Sandeep CLEAN Venkat (AK Point File Size < 300)<br /> 1344 10/09/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1345 10/16/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1346 10/23/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1347 10/30/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1348 11/06/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1349 11/13/2005 Sandeep CLEAN Venkat (AK Point File Size < 300) <br /> 1350 11/20/2005 Sandeep CLEAN Venkat (AK Point File Size < 400) <br /> 1351 11/27/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1352 12/04/2005 Sandeep CLEAN Venkat (AK Point File Size < 300) <br /> 1353 12/11/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1354 12/18/2005 Sandeep CLEANING Venkat<br /> 1356 12/25/2005 Sandeep CLEANING Venkat<br /> </pre><br /> <br /> ===Older Stuff===<br /> <pre><br /> week # start date last processed who status<br /> ****************************************************************<br /> ****************************************************************<br /> ***************************2002*********************************<br /> **************************EARTHQUAKE****************************<br /> 1189 10/20/02 02/26/05 Josh PENDING<br /> 1190 10/27/02 Josh PENDING<br /> 1191 11/03/02 03/04/05 Josh DONE<br /> 1192 11/10/02 03/11/05 Josh DONE<br /> 1193 11/17/02 03/11/05 Josh DONE<br /> 1194 11/24/02 03/11/05 Josh DONE<br /> 1195 12/01/02 03/11/05 Josh RUNNING<br /> 1196 12/08/02 03/11/05 Josh DONE<br /> 1197 12/15/02 03/11/05 Josh DONE<br /> 1198 12/22/02 03/12/05 Josh DONE<br /> 1199 12/29/02 03/12/05 Josh DONE<br /> <br /> *************************2003***********************************<br /> <br /> 1200 01/05/03 03/12/05 Josh DONE<br /> 1201 01/12/03 03/12/05 Josh DONE<br /> 1202 01/19/03 03/15/05 Josh RUNNING<br /> 1203 01/26/03 03/14/05 Josh DONE<br /> 1204 02/02/03 03/14/05 Josh DONE<br /> 1205 02/09/03 Josh PENDING<br /> 1206 02/16/03 Josh PENDING<br /> 1207 02/23/03 Josh PENDING<br /> 1208 03/02/03 02/26/05 Josh ALMOST CLEAN<br /> 1209 03/09/03 02/26/05 Josh ALMOST CLEAN<br /> 1210 03/16/03 02/26/05 Josh NEEDS CLEAN<br /> 1211 03/23/03 02/27/05 Josh DONE<br /> 1212 03/30/03 02/26/05 Josh DONE<br /> 1213 04/06/03 03/12/05 Josh RUNNING<br /> 1214 04/13/03 02/26/05 Josh CLEANED<br /> 1215 04/20/03 02/27/05 Josh CLEANED<br /> 1216 04/27/03 02/26/05 Josh PENDING<br /> 1217 05/04/03 02/26/05 Josh NEEDS CLEAN<br /> 1218 05/11/03 02/27/05 Josh NEEDS CLEAN<br /> 1219 05/18/03 02/27/05 Josh WORKING<br /> 1220 05/25/03 02/27/05 Josh PENDING<br /> 1221 06/01/03 Josh PENDING<br /> 1222 06/08/03 Josh PENDING<br /> 1223 06/15/03 Josh PENDING<br /> 1224 06/22/03 Josh PENDING<br /> 1225 06/29/03 02/26/05 Josh FAILED<br /> 1226 07/06/03 02/26/05 Josh ALMOST CLEAN<br /> 1227 07/13/03 02/26/05 Josh FAILED<br /> 1228 07/20/03 Josh FAILED<br /> 1229 07/27/03 11/10/05 Tom Submitted <br /> 1230 08/03/03 Josh FAILED<br /> 1231 08/10/03 Josh FAILED<br /> 1232 08/17/03 11/10/05 Tom Submitted <br /> 1233 08/24/03 02/26/05 Josh ALMOST CLEAN<br /> 1234 08/31/03 02/26/05 Josh ALMOST CLEAN<br /> 1235 09/07/03 02/26/05 Josh ALMOST CLEAN<br /> 1236 09/14/03 02/26/05 Josh ALMOST CLEAN<br /> 1237 09/21/03 02/26/05 Josh NEEDS CLEAN<br /> 1238 09/28/03 02/26/05 Josh NEEDS CLEAN<br /> 1239 10/05/03 02/26/05 Josh WORKING<br /> 1240 10/12/03 02/26/05 Josh PENDING<br /> 1241 10/19/03 02/26/05 Josh NEEDS CLEAN<br /> 1242 10/26/03 02/26/05 Josh ALMOST CLEAN<br /> 1243 11/02/03 02/26/05 Josh NEEDS CLEAN<br /> 1244 11/09/03 02/26/05 Josh NEEDS CLEAN<br /> 1245 11/16/03 02/26/05 Josh ALMOST CLEAN<br /> 1246 11/23/03 02/26/05 Josh ALMOST CLEAN<br /> 1247 11/30/03 02/26/05 Josh ALMOST CLEAN<br /> 1248 12/07/03 02/26/05 Josh NEEDS CLEAN<br /> 1249 12/14/03 02/26/05 Josh NEEDS CLEAN<br /> 1250 12/21/03 02/26/05 Josh NEEDS CLEAN<br /> 1251 12/28/03 02/26/05 Josh WORKING<br /> <br /> ***************************2004*********************************<br /> <br /> 1253 01/11/04 02/26/05 Josh PENDING<br /> 1254 01/18/04 Josh PENDING<br /> 1255 01/25/04 Josh NEEDS<br /> 1256 02/01/04 Josh PENDING<br /> 1257 02/08/04 Josh PENDING<br /> 1258 02/15/04 Josh PENDING<br /> 1259 02/22/04 Josh PENDING<br /> 1260 02/29/04 Josh PENDING<br /> 1261 03/07/04 02/26/05 Josh PENDING<br /> 1262 03/14/04 02/26/05 Josh NEEDS CLEAN<br /> 1263 03/21/04 02/26/05 Josh NEEDS CLEAN<br /> 1264 03/28/04 02/26/05 Josh NEEDS CLEAN<br /> 1265 04/04/04 02/26/05 Josh FAILED No files found, needs re<br /> run<br /> 1266 04/11/04 02/26/05 Josh FAILED No files found, needs re<br /> run<br /> 1267 04/18/04 02/26/05 Josh NEEDS CLEAN<br /> 1268 04/25/04 02/26/05 Josh NEEDS CLEAN<br /> 1269 05/02/04 02/26/05 Josh NEEDS CLEAN<br /> 1270 05/09/04 02/26/05 Josh NEEDS CLEAN<br /> 1271 05/16/04 02/26/05 Josh NEEDS CLEAN<br /> 1272 05/23/04 02/26/05 Josh NEEDS CLEAN<br /> 1273 05/30/04 02/26/05 Josh NEEDS CLEAN<br /> 1274 06/06/04 02/26/05 Josh NEEDS CLEAN<br /> 1275 06/13/04 02/26/05 Josh NEEDS CLEAN<br /> 1276 06/20/04 02/27/05 Samik DONE<br /> 1277 06/27/04 03/19/05 Jeff NEEDS CLEAN<br /> 1278 07/04/04 03/19/05 Jeff NEEDS CLEAN<br /> 1279 07/11/04 03/19/05 Jeff NEEDS CLEAN<br /> 1280 07/18/04 03/19/05 Jeff NEEDS CLEAN<br /> 1281 07/25/04 03/19/05 Jeff NEEDS CLEAN<br /> 1282 08/01/04 Josh PENDING<br /> 1283 08/08/04 Josh PENDING<br /> 1284 08/15/04 Josh PENDING<br /> 1285 08/22/04 Josh PENDING<br /> 1286 08/29/04 Josh PENDING<br /> 1287 09/05/04 Josh PENDING<br /> 1288 09/12/04 Josh PENDING<br /> 1289 09/19/04 03/19/05 Jeff ??<br /> 1290 09/26/04 Josh PENDING<br /> 1291 10/03/04 Josh PENDING<br /> 1292 10/10/04 03/19/05 Jeff ??<br /> 1293 10/17/04 Josh PENDING<br /> 1294 10/24/04 03/19/05 Jeff ??<br /> 1295 10/31/04 03/25/05 Tom CLEAN<br /> 1296 11/07/04 04/07/05 Tom Cleaning<br /> 1297 11/14/04 03/19/05 Jeff ??<br /> 1298 11/21/04 NEEDS CLEAN<br /> 1299 11/28/04 NEEDS CLEAN<br /> 1300 12/05/04 08/16/05 Pravee CLEAN<br /> 1301 12/12/04 08/19/05 Pravee CLEAN<br /> 1302 12/19/04 08/19/05 Pravee CLEAN trivikram(tibet) CLEAN 07/26/2006<br /> 1303 12/26/04 08/26/05 Pravee CLEAN <br /> </pre><br /> <br /> ===Archaic (pre-1996)===<br /> <pre><br /> week # start date last processed who status<br /> ****************************************************************<br /> At the moment, Jeff is dealing with these.<br /> </pre></div>

Yuning http://gps.alaska.edu/internal/index.php?title=GPS_analysis_system&diff=1563 GPS analysis system 2008-07-30T20:32:22Z

<p>Yuning: /* Running Solutions */</p> <hr /> <div>We use a GPS data analysis system based on the [http://sideshow.jpl.nasa.gov GIPSY] software developed at JPL. Most of the GIPSY programs are called by [[shell scripts]] written by Jeff Freymueller. Using these scripts, we can analyze a large amount of data either as part of network solutions or in Precise Point Positioning (PPP) mode.<br /> <br /> ===Where do you put RINEX files?===<br /> RINEX files should be put into the hopper, <code>$RAWDATA/hopper</code>. What, you don't have RINEX files yet? See [[RINEXing]]. Once files are in the hopper, you can either let the first processing stages happen automatically overnight (see next section), or run the <code>autofront</code> and <code>autoclean</code> programs manually.<br /> <br /> ===What happens automatically?===<br /> <br /> Quite a lot.<br /> <br /> Autoftp runs every night beginning at 6pm local time and fetches data files. These are placed into the '''hopper''' ($RAWDATA/hopper), a directory where all data files are put for entry into the system and processing. Autofront then runs at midnight to process all files in the hopper, including any placed there manually (from campaigns, for example). Finally, autoclean runs at 4am local to carry out automated screening for cycle slips and other bad data.<br /> <br /> ====Autoftp====<br /> <br /> Autoftp is an efficient data-fetching tool that uses wget to automatically get data from any of several internet GPS data archives. It reads a list of desired sites from a ''request file'', which contains the date in the filename, and attempts to find and download data from as many sites as possible. It is intended to run automatically on a daily basis under cron, and when acccompanied by another simple program to generate a standard request file every day, it can easily fetch a standard set of sites on a daily basis for analysis. Because it keeps track in the request file of sites that it has found already, autoftp can be run multiple times with the same request file and it will not repeatedly fetch data. This is ideal for the real world, in which data from some sites are available rapidly while data from other sites may require many hours or days to become available.<br /> <br /> ====Autofront====<br /> <br /> Autofront is a script intended to run under cron that carried out the initial "front end" processing on a set of GPS data files. When executed, it will process all files in the '''hopper''' directory, and will place each resulting qm file into the appropriate week directory.<br /> <br /> Autofront runs the following steps<br /> 1. Checks on the validity of RINEX file and repair of some common problems.<br /> 2. Depending on receiver type, clockprep -fixtags<br /> 3. (optional, presently not default) PhasEdit<br /> 4. ninja<br /> <br /> ====Autoclean====<br /> <br /> Autoclean carries out automated cleaning of cycle slips, based on point positioning solutions. It is quite effective and at present it rarely misses cycle slips unless they are smaller than its minimum tolerance (10 cm). Autoclean operates on an ''edit-request'' file, which contains the name of the directory (week directory) and a list of qm files that need to be cleaned. It will clean all files on the list as long as orbits and clocks are available, and it marks off files that have been cleaned so that it can safely be run multiple times.<br /> <br /> Autoclean operates in an iterative mode. It's zeroth iteration is to do a pseudorange-only solution and identify and delete extremely bad pseudorange data. In this step it uses a tolerance that catches only grossly biased data. (Explain it). It then carries out 1 or more iterations of screening the phase data. In each iteration, it uses postbreak to identify discontinuities in the residuals of a point positioning solution. Postbreak is run with an adaptive tolerance (minimum 10 cm), and it is critical that my slightly modified version of postbreak be used. If any cycle slips are discovered, they are flagged and another iteration is run. Autoclean runs a maximum of 4 iterations on the phase data.<br /> <br /> ===Where do the data files go?===<br /> Data files from each station are stored in the QM format that is native to GIPSY. QM files (and all other) files are stored in directories by GPS week. For each [[week_directory|week directory]] there are several [[subdirectories]]; qm files are stored in <code>$ANALYSIS/wwww/qm</code>, where <code>wwww</code> is the 4 character GPS week number (with a leading zero if needed).<br /> <br /> ===Running Solutions===<br /> In the [[subdirectories|flt]] directory for each [[week directory|week]] there will (hopefully) be a UNIX script called<br><br /> ''make-*''<br><br /> This script runs another script called<br><br /> ''standard_*_solution''<br><br /> which again runs another script called<br><br /> ''solve''<br><br /> for each [[subnets | network of stations]] (see each subnet with [[Subnets_GoogleEarth | Google Earth]]) for each day. The solve script runs solutions for each of these networks based on the data from sites in the network that are available in the qm directory.<br /> <br /> To run solutions, copy the ''make'' script to a file called ''make-flt'' (for example).<br /> <br /> Check that the ''make-flt'' script contains all the days that you want to run.<br /> <br /> Check which [[Linux Computer System | computer]] is free to run the script (to do so, type:)<br /> check-solves<br /> log on to a free computer and type<br /> submit make-flt<br /> <br /> As the script runs, files will appear in the [[subdirectories|flt]] directory for each [[subnets|network]] for each day. Usually<br /> this script will have been run once [[#What happens automatically? | automatically]], so there will often already be files in the [[subdirectories|flt]]<br /> directory ready to be cleaned and then re-run.<br /> <br /> <br /> Solve, a very flexible script. (link to detailed help)<br /> <br /> Philosophy of solve<br /> <br /> Subnet files and campaign files<br /> <br /> Standard solutions<br /> <br /> (text of standard_Alaska_solution)<br /> <br /> Running several days at once: make-make-flt and make-alaska<br /> <br /> (text of a standard make-alaska file and variant)<br /> <br /> Running several weeks at once<br /> <br /> (text of sample rerun-* file)<br /> <br /> ===Cleaning Solutions===<br /> <br /> Sometimes bad data (outliers and cycle slips) make it past the automatic editors. When this<br /> happens the bad data are removed from the qm files by either deleting points or by inserting<br /> new phase ambiguities to deal with cycle slips. The steps, commands and scrips to use are somewhat explained [[How to clean a solution? | here]]. Once the data are cleaned, the files should be deleted from the [[subdirectories|flt]] directory and the solutions re-run (run <code>make-flt</code> again). Usually you will have to go through 2-3<br /> iterations of the cleaning-rerunning cycle. To be clean, the .point files for a solution do not<br /> exist or are small (below 1000 bytes). Once a solution is clean the files should remain in<br /> the [[subdirectories|flt]] directory and the lines to rerun that solution should be deleted from the <code>make-flt</code> file.<br /> <br /> Initial Explanation of terms<br /> <br /> Expected residuals from a clean solution<br /> <br /> Automated screening: postfit, the point file, postbreak<br /> <br /> Checking for bad pseudorange data: badp, [[How to clean a solution?|allbadp]]<br /> <br /> Removing biased pseudorange data: [[How to clean a solution?|del_pcode_arc]]<br /> <br /> Automatically identified cycle slips: breaks, [[How to clean a solution?|allbreaks]]<br /> <br /> Quickly scanning through residuals: short_hand<br><br /> The data problems can be identified and<br /> fixed using the program<br /> [[short_hand]] <br /> (follow the link to read about and ask for help to get started with this program).<br> <br /> Limitations of short_hand<br /> <br /> Manually checking residuals and fixing [[problem stations | problems]]<br /> <br /> ===Procedure for Running Solutions for a week for the first time===<br /> <br /> A few special things need to be done the very first time solutions in a week are run. First, you need to make up a script to run all days of the week. This may need to be edited if the JPL final orbits are not available at the time. The <code>standard_Alaska_solution</code> uses the non-fiducial orbits and thus requires that the final JPL orbits be present. If they are not, you can run <code>rapid_Alaska_solution</code> instead. <br /> <br /> Then, the log files from autoclean should be moved away to a subdirectory, and any problem stations identified by autoclean should be checked. Then, you are ready to run the solutions.<br /> <br /> First, make a script to run solutions. For example, to make a script to run all days of the week for the Alaska solution:<br /> <pre><br /> cd $ANALYSIS<br /> make-make-flt 1381<br /> cd 1381/flt<br /> vi make-alaska<br /> # Edit the file if needed so that you are ready to run the rapid solutions.<br /> <br /> cat make-alaska<br /> #!/bin/csh -f<br /> #<br /> setenv CAMP $ANALYSIS/1381<br /> #<br /> #standard_Alaska_solution 06jul01<br /> #standard_Alaska_solution 06jun25<br /> #standard_Alaska_solution 06jun26<br /> #standard_Alaska_solution 06jun27<br /> #standard_Alaska_solution 06jun28<br /> #standard_Alaska_solution 06jun29<br /> #standard_Alaska_solution 06jun30<br /> #<br /> rapid_Alaska_solution 06jul01<br /> rapid_Alaska_solution 06jun25<br /> rapid_Alaska_solution 06jun26<br /> rapid_Alaska_solution 06jun27<br /> rapid_Alaska_solution 06jun28<br /> rapid_Alaska_solution 06jun29<br /> rapid_Alaska_solution 06jun30<br /> <br /> </pre><br /> <br /> The script <code>make-make-flt</code> finds all unique dates for qm files in that week's directory, and uses that to generate the script, so if you run it before the end of the week you will get a partial script. If the final JPL orbits are not yet present, you will need to edit the script to change "standard" ro "rapid". Or better yet, copy all the lines and comment one set out, then modify the others to read "rapid_Alaska_solution <date>".<br /> <br /> Next, make a subdirectory called <code>logfiles</code>, and move all of autoclean's logfiles into it. You will need to use two separate <code>mv</code> commands because the list of files is too big for one.<br /> <br /> <pre><br /> mkdir logfiles<br /> mv *____*.i1* logfiles<br /> mv *____*.i* logfiles<br /> </pre><br /> <br /> Now look for a file called <code>make-problems</code>, which lists all files that autoclean had a problem with. Sometimes these files are almost clean, but sometimes they are full of junk or horribly mangled by the automated editing. There should be PPP solutions already run for these files, so they are ready to be checked.<br /> <br /> Set the <code>CAMP</code> variable (if not set): <br /> <pre><br /> setenv CAMP $ANALYSIS/wwww<br /> </pre><br /> Again, <code>wwww</code> is the 4-digit GPS-week.<br /> <br /> Now run the solutions. The first time you run the solutions, look at the residuals very carefully before trying <code>short_hand</code>. Uncompress the postlog, postfit and postbreak files, and then use <code>allbadp</code> to check the pseudorange and <code>allbreaks</code> to check for major cycle slips.<br /> <br /> A very common problem is that for several stations per week, there will be one satellite arc of pseudorange data that all have residuals of roughly 2000 cm. If you see these, don't delete the data, but instead run del_pcode_arc to remove only the pseudorange data. I am not sure why these show up, but it could be either a hardware channel bias or a pre-processing glitch. They happen much more often with Ashtechs than any others, and are particuarly common with the US Coast Guard CORS sites. In the <code>qm</code> directory,<br /> <br /> <pre><br /> del_pcode_arc *02gus2* GUS2 GPS41<br /> </pre><br /> <br /> If you just run <code>short_hand</code> without looking, it will probably either throw out all the pseudorange for one site, or delete a lot of data (phase and pseudorange) where only the pseudorange needs to be deleted. So don't do that. Then I delete a batch of bad pseudorange data to get the number of pseudorange outliers under control for the next run.<br /> <br /> <pre><br /> cd $ANALYSIS/1381/flt<br /> gunzip *alaska*post*<br /> allbadp<br /> allbreaks<br /> # Based on this, run del_pcode_arc as above, and add ambiguities manually if needed.<br /> #<br /> delete_allbadp 50<br /> # This creates a file called delete.<br /> vi delete<br /> # Remove lines for any points for which you have already run del_pocde_arc.<br /> cd ../qm<br /> sh ../flt/delete<br /> </pre><br /> <br /> At this point, don't worry too much about phase outliers. Basically we are trying to get the number of pseudorange outliers down into the range where <code>short_hand</code> will do the right thing when we run it later. Now may be a good time to run <code>Alaska_cleaning_solution $date</code>, which runs a smaller and much faster solution including the sites that most often need some cleaning.<br /> <br /> <br /> ===Data Backup===<br /> <br /> RINEX file backups.<br /> There are either 1 or 2 separate backups of the raw rinex files. For data we collected<br /> ourselves, a copy of the original rinex files can be found in either the campaign<br /> directory (/gps/akda/Campaigns/Data.2007/<project>, where <project> is the project name,<br /> and Data.2007 will change with the year), or in the continuous site ftp area<br /> (/gps/akda/Permanent/2007/260/, where 2007 is the year and 160 is the day of year). Also,<br /> every rinex file put through the hopper is moved to a directory like $RAWDATA/2007/260/<br /> (again, year and day of year may change). However, the $RAWDATA/2007/260/ directories are<br /> not really archived and eventually they will be deleted. But in practice we have most of<br /> the last few years of rinex files online in case something goes wrong.<br /> <br /> QM file backups.<br /> Before autoclean makes any changes to a qm file, it copies the file to a subdirectory<br /> called "original" in the qm directory. so if you completely destroy a qm file by<br /> accident, you can still go back the original version. Of course, that loses all editing<br /> done to the file, but at least the original data can be recovered easily. In general, it<br /> is not a good idea to go back to the version in the original subdirectory unless you know<br /> what you are doing, because doing that can make a lot more work for everyone. Mostly we<br /> do that when files have been mangled by autoclean. It is actually hard to mangle data<br /> files using our usual editing procedures.<br /> <br /> <br /> <br /> ===Customized Solutions===<br /> <br /> Sometimes customized solutions are required for various reasons. This link will provide some strategies that may improve your situation.<br /> <br>[[Kinematic Processing]]<br /> <br>[[Ambiguity Resolution]]<br /> <br /> ===Products / file contents===<br /> <br /> Where to find certain information and what are the structure / content of output files? It is started to be summarized on the [[files | files]] page.</div>

Yuning http://gps.alaska.edu/internal/index.php?title=GeodesyLab:Community_Portal&diff=1583 GeodesyLab:Community Portal 2008-07-30T20:26:16Z

<p>Yuning: </p> <hr /> <div>=== [[Alaska Volcano Observatory]] ===<br /> This links to pages that deal with observatory duties, processes and web-pages.<br /> <br /> === [[Matlab Users]]: Modeling, etc. ===<br /> Handy Matlab functions and how to use them<br /> <br /> === [[Subnets_GoogleEarth]] ===<br /> The ".kml" files for each subnet are edit, so we can "open" these files with Goolge Earth and play around with them.</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Subnets&diff=1574 Subnets 2008-07-30T20:25:53Z

<p>Yuning: </p> <hr /> <div>We have several (sub)networks, which enables us to process the solution of a certain set of stations without conflicting the limits set by computer resources.<br /> <br /> Those subnets are: <br /> <br /> {|<br /> !align="left" !width="100" | name || !width="200" | where || !width="50" | map <br /> |- <br /> | alaska <br /> | align="center" | Alaska region<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/Alaska.subnet.pdf alaska]<br /> |-<br /> | casa <br /> | align="center" | South America<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/CASA.subnet.pdf casa]<br /> |-<br /> | TIGAswp <br /> | align="center" | South-West Alaska<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/TIGAswp.subnet.pdf TIGAswp]<br /> |-<br /> | tibet<br /> |<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/Tibet.subnet.pdf tibet]<br /> |-<br /> | NEAsia<br /> | align="center" | North-East Asia<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/NEAsia.subnet.pdf NEAsia]<br /> |-<br /> | NOAM<br /> | align="center" | North America<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/NOAM.subnet.pdf NOAM]<br /> <br /> |}<br /> <br /> <br /> To see a plot for each subnet click on the subnet name under "map".<br /> <br /> You can also look at our subnets using Google Earth (see [[Subnets_GoogleEarth|here]]).</div>

Yuning http://gps.alaska.edu/internal/index.php?title=GeodesyLab:Community_Portal&diff=621 GeodesyLab:Community Portal 2008-07-30T20:24:23Z

<p>Yuning: </p> <hr /> <div>=== [[Alaska Volcano Observatory]] ===<br /> This links to pages that deal with observatory duties, processes and web-pages.<br /> <br /> === [[Matlab Users]]: Modeling, etc. ===<br /> Handy Matlab functions and how to use them<br /> <br /> === [[subnets_GoogleEarth]] ===<br /> The ".kml" files for each subnet are edit, so we can "open" these files with Goolge Earth and play around with them.</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Subnets_GoogleEarth&diff=1601 Subnets GoogleEarth 2008-07-30T20:18:09Z

<p>Yuning: </p> <hr /> <div>The ".kml" files have been edit for ''Google Earth'', then you can "open" these files with ''Goolge Earth'' and play around with them.<br /> <br /> Download ".kml" files here:<br /> <br /> Alaska: <br /> <br /> [http://gps.alaska.edu/~yuning/subnets/Alaska.kml "Alaska.kml"]<br /> <br /> [http://gps.alaska.edu/~yuning/subnets/Alaska.jpg "Alaska.jpg"]<br /> <br /> CASA: <br /> <br /> [http://gps.alaska.edu/~yuning/subnets/CASA.kml "CASA.kml"]<br /> <br /> [http://gps.alaska.edu/~yuning/subnets/CASA.jpg "CASA.jpg"]<br /> <br /> EurAf: <br /> <br /> [http://gps.alaska.edu/~yuning/subnets/EurAf.kml "EurAf.kml"]<br /> <br /> [http://gps.alaska.edu/~yuning/subnets/EurAf.jpg "EurAf.jpg"]<br /> <br /> Greenland: <br /> <br /> [http://gps.alaska.edu/~yuning/subnets/Greenland.kml "Greenland.kml"]<br /> <br /> [http://gps.alaska.edu/~yuning/subnets/Greenland.jpg "Greenland.jpg"]<br /> <br /> NCal: <br /> <br /> [http://gps.alaska.edu/~yuning/subnets/NCal.kml "NCal.kml"]<br /> <br /> [http://gps.alaska.edu/~yuning/subnets/NCal.jpg "NCal.jpg"]<br /> <br /> NEAsia: <br /> <br /> [http://gps.alaska.edu/~yuning/subnets/NEAsia.kml "NEAsia.kml"]<br /> <br /> [http://gps.alaska.edu/~yuning/subnets/NEAsia.jpg "NEAsia.jpg"]<br /> <br /> NOAM: <br /> <br /> [http://gps.alaska.edu/~yuning/subnets/NOAM.kml "NOAM.kml"]<br /> <br /> [http://gps.alaska.edu/~yuning/subnets/NOAM.jpg "NOAM.jpg"]<br /> <br /> Tibet: <br /> <br /> [http://gps.alaska.edu/~yuning/subnets/Tibet.kml "Tibet.kml"]<br /> <br /> [http://gps.alaska.edu/~yuning/subnets/Tibet.jpg "Tibet.jpg"]<br /> <br /> TIGAswp: <br /> <br /> [http://gps.alaska.edu/~yuning/subnets/TIGAswp.kml "TIGAswp.kml"]<br /> <br /> [http://gps.alaska.edu/~yuning/subnets/TIGAswp.jpg "TIGAswp.jpg"]</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Subnets_GoogleEarth&diff=618 Subnets GoogleEarth 2008-07-30T20:17:24Z

<p>Yuning: </p> <hr /> <div>The ".kml" files have been edit for ''Google Earth'', then you can "open" these files with ''Goolge Earth'' and play around with them.<br /> <br /> Download ".kml" files here:<br /> <br /> Alaska: <br /> [http://gps.alaska.edu/~yuning/subnets/Alaska.kml "Alaska.kml"] [http://gps.alaska.edu/~yuning/subnets/Alaska.jpg "Alaska.jpg"]<br /> <br /> CASA: <br /> [http://gps.alaska.edu/~yuning/subnets/CASA.kml "CASA.kml"]<br /> [http://gps.alaska.edu/~yuning/subnets/CASA.jpg "CASA.jpg"]<br /> <br /> EurAf: <br /> [http://gps.alaska.edu/~yuning/subnets/EurAf.kml "EurAf.kml"]<br /> [http://gps.alaska.edu/~yuning/subnets/EurAf.jpg "EurAf.jpg"]<br /> <br /> Greenland: <br /> [http://gps.alaska.edu/~yuning/subnets/Greenland.kml "Greenland.kml"]<br /> [http://gps.alaska.edu/~yuning/subnets/Greenland.jpg "Greenland.jpg"]<br /> <br /> NCal: <br /> [http://gps.alaska.edu/~yuning/subnets/NCal.kml "NCal.kml"]<br /> [http://gps.alaska.edu/~yuning/subnets/NCal.jpg "NCal.jpg"]<br /> <br /> NEAsia: <br /> [http://gps.alaska.edu/~yuning/subnets/NEAsia.kml "NEAsia.kml"]<br /> [http://gps.alaska.edu/~yuning/subnets/NEAsia.jpg "NEAsia.jpg"]<br /> <br /> NOAM: <br /> [http://gps.alaska.edu/~yuning/subnets/NOAM.kml "NOAM.kml"]<br /> [http://gps.alaska.edu/~yuning/subnets/NOAM.jpg "NOAM.jpg"]<br /> <br /> Tibet: <br /> [http://gps.alaska.edu/~yuning/subnets/Tibet.kml "Tibet.kml"]<br /> [http://gps.alaska.edu/~yuning/subnets/Tibet.jpg "Tibet.jpg"]<br /> <br /> TIGAswp: <br /> [http://gps.alaska.edu/~yuning/subnets/TIGAswp.kml "TIGAswp.kml"]<br /> [http://gps.alaska.edu/~yuning/subnets/TIGAswp.jpg "TIGAswp.jpg"]</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Subnets_GoogleEarth&diff=617 Subnets GoogleEarth 2008-07-30T20:13:51Z

<p>Yuning: </p> <hr /> <div>The ".kml" files have been edit for ''Google Earth'', then you can "open" these files with ''Goolge Earth'' and play around with them.<br /> <br /> Download ".kml" files here:<br /> <br /> Alaska: [http://gps.alaska.edu/~yuning/subnets/Alaska.kml "Alaska.kml"] [http://gps.alaska.edu/~yuning/subnets/Alaska.jpg "Alaska.jpg"]<br /> <br /> CASA: [http://gps.alaska.edu/~yuning/subnets/CASA.kml "CASA.kml"]<br /> <br /> EurAf: [http://gps.alaska.edu/~yuning/subnets/EurAf.kml "EurAf.kml"]<br /> <br /> Greenland: [http://gps.alaska.edu/~yuning/subnets/Greenland.kml "Greenland.kml"]<br /> <br /> NCal: [http://gps.alaska.edu/~yuning/subnets/NCal.kml "NCal.kml"]<br /> <br /> NEAsia: [http://gps.alaska.edu/~yuning/subnets/NEAsia.kml "NEAsia.kml"]<br /> <br /> NOAM: [http://gps.alaska.edu/~yuning/subnets/NOAM.kml "NOAM.kml"]<br /> <br /> Tibet: [http://gps.alaska.edu/~yuning/subnets/Tibet.kml "Tibet.kml"]<br /> <br /> TIGAswp: [http://gps.alaska.edu/~yuning/subnets/TIGAswp.kml "TIGAswp.kml"]</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Subnets_GoogleEarth&diff=616 Subnets GoogleEarth 2008-07-30T20:13:16Z

<p>Yuning: </p> <hr /> <div>The ".kml" files have been edit for ''Google Earth'', then you can "open" these files with ''Goolge Earth'' and play around with them.<br /> <br /> Download ".kml" files here:<br /> <br /> Alaska: [http://gps.alaska.edu/~yuning/subnets/Alaska.kml "Alaska.kml"]<br /> [http://gps.alaska.edu/~yuning/subnets/Alaska.jpg "Alaska.jpg"]<br /> <br /> CASA: [http://gps.alaska.edu/~yuning/subnets/CASA.kml "CASA.kml"]<br /> <br /> EurAf: [http://gps.alaska.edu/~yuning/subnets/EurAf.kml "EurAf.kml"]<br /> <br /> Greenland: [http://gps.alaska.edu/~yuning/subnets/Greenland.kml "Greenland.kml"]<br /> <br /> NCal: [http://gps.alaska.edu/~yuning/subnets/NCal.kml "NCal.kml"]<br /> <br /> NEAsia: [http://gps.alaska.edu/~yuning/subnets/NEAsia.kml "NEAsia.kml"]<br /> <br /> NOAM: [http://gps.alaska.edu/~yuning/subnets/NOAM.kml "NOAM.kml"]<br /> <br /> Tibet: [http://gps.alaska.edu/~yuning/subnets/Tibet.kml "Tibet.kml"]<br /> <br /> TIGAswp: [http://gps.alaska.edu/~yuning/subnets/TIGAswp.kml "TIGAswp.kml"]</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Subnets_GoogleEarth&diff=615 Subnets GoogleEarth 2008-07-30T20:12:36Z

<p>Yuning: </p> <hr /> <div>The ".kml" files have been edit for ''Google Earth'', then you can "open" these files with ''Goolge Earth'' and play around with them.<br /> <br /> Download ".kml" files here:<br /> <br /> Alaska: [http://gps.alaska.edu/~yuning/subnets/Alaska.kml "Alaska.kml"]<br /> [http://gps.alaska.edu/~yuning/subnets/Alaska.jpg "Alaska.jpg"]<br /> <br /> CASA: [http://gps.alaska.edu/~yuning/subnets/CASA.kml "CASA.kml"]<br /> <br /> EurAf: [http://gps.alaska.edu/~yuning/subnets/EurAf.kml "EurAf.kml"]<br /> <br /> Greenland: [http://gps.alaska.edu/~yuning/subnets/Greenland.kml "Greenland.kml"]<br /> <br /> NCal: [http://gps.alaska.edu/~yuning/subnets/NCal.kml "NCal.kml"]<br /> <br /> NEAsia: [http://gps.alaska.edu/~yuning/subnets/NEAsia.kml "NEAsia.kml"]<br /> <br /> NOAM: [http://gps.alaska.edu/~yuning/subnets/NOAM.kml "NOAM.kml"]<br /> <br /> Tibet: [http://gps.alaska.edu/~yuning/subnets/Tibet.kml "Tibet.kml"]<br /> <br /> TIGAswp: [http://gps.alaska.edu/~yuning/subnets/TIGAswp.kml "TIGAswp.kml"]</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Subnets_GoogleEarth&diff=614 Subnets GoogleEarth 2008-07-30T20:11:03Z

<p>Yuning: </p> <hr /> <div>The ".kml" files have been edit for ''Google Earth'', then you can "open" these files with ''Goolge Earth'' and play around with them.<br /> <br /> Download ".kml" files here:<br /> <br /> Alaska: [http://gps.alaska.edu/~yuning/subnets/Alaska.kml "Alaska.kml"]<br /> <br /> [[Image:http://gps.alaska.edu/~yuning/subnets/Alaska.jpg]]<br /> <br /> CASA: [http://gps.alaska.edu/~yuning/subnets/CASA.kml "CASA.kml"]<br /> <br /> EurAf: [http://gps.alaska.edu/~yuning/subnets/EurAf.kml "EurAf.kml"]<br /> <br /> Greenland: [http://gps.alaska.edu/~yuning/subnets/Greenland.kml "Greenland.kml"]<br /> <br /> NCal: [http://gps.alaska.edu/~yuning/subnets/NCal.kml "NCal.kml"]<br /> <br /> NEAsia: [http://gps.alaska.edu/~yuning/subnets/NEAsia.kml "NEAsia.kml"]<br /> <br /> NOAM: [http://gps.alaska.edu/~yuning/subnets/NOAM.kml "NOAM.kml"]<br /> <br /> Tibet: [http://gps.alaska.edu/~yuning/subnets/Tibet.kml "Tibet.kml"]<br /> <br /> TIGAswp: [http://gps.alaska.edu/~yuning/subnets/TIGAswp.kml "TIGAswp.kml"]</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Subnets_GoogleEarth&diff=613 Subnets GoogleEarth 2008-07-30T20:10:37Z

<p>Yuning: </p> <hr /> <div>The ".kml" files have been edit for ''Google Earth'', then you can "open" these files with ''Goolge Earth'' and play around with them.<br /> <br /> Download ".kml" files here:<br /> <br /> Alaska: [http://gps.alaska.edu/~yuning/subnets/Alaska.kml "Alaska.kml"]<br /> <br /> <td><br /> [[Image:http://gps.alaska.edu/~yuning/subnets/Alaska.jpg]]<br /> </td><br /> <br /> CASA: [http://gps.alaska.edu/~yuning/subnets/CASA.kml "CASA.kml"]<br /> <br /> EurAf: [http://gps.alaska.edu/~yuning/subnets/EurAf.kml "EurAf.kml"]<br /> <br /> Greenland: [http://gps.alaska.edu/~yuning/subnets/Greenland.kml "Greenland.kml"]<br /> <br /> NCal: [http://gps.alaska.edu/~yuning/subnets/NCal.kml "NCal.kml"]<br /> <br /> NEAsia: [http://gps.alaska.edu/~yuning/subnets/NEAsia.kml "NEAsia.kml"]<br /> <br /> NOAM: [http://gps.alaska.edu/~yuning/subnets/NOAM.kml "NOAM.kml"]<br /> <br /> Tibet: [http://gps.alaska.edu/~yuning/subnets/Tibet.kml "Tibet.kml"]<br /> <br /> TIGAswp: [http://gps.alaska.edu/~yuning/subnets/TIGAswp.kml "TIGAswp.kml"]</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Subnets_GoogleEarth&diff=612 Subnets GoogleEarth 2008-07-30T19:57:20Z

<p>Yuning: </p> <hr /> <div>The ".kml" files have been edit for ''Google Earth'', then you can "open" these files with ''Goolge Earth'' and play around with them.<br /> <br /> Download ".kml" files here:<br /> <br /> Alaska: [http://gps.alaska.edu/~yuning/subnets/Alaska.kml "Alaska.kml"]<br /> <br /> [[Image:http://gps.alaska.edu/~yuning/subnets/Alaska.jpg]]<br /> <br /> CASA: [http://gps.alaska.edu/~yuning/subnets/CASA.kml "CASA.kml"]<br /> <br /> EurAf: [http://gps.alaska.edu/~yuning/subnets/EurAf.kml "EurAf.kml"]<br /> <br /> Greenland: [http://gps.alaska.edu/~yuning/subnets/Greenland.kml "Greenland.kml"]<br /> <br /> NCal: [http://gps.alaska.edu/~yuning/subnets/NCal.kml "NCal.kml"]<br /> <br /> NEAsia: [http://gps.alaska.edu/~yuning/subnets/NEAsia.kml "NEAsia.kml"]<br /> <br /> NOAM: [http://gps.alaska.edu/~yuning/subnets/NOAM.kml "NOAM.kml"]<br /> <br /> Tibet: [http://gps.alaska.edu/~yuning/subnets/Tibet.kml "Tibet.kml"]<br /> <br /> TIGAswp: [http://gps.alaska.edu/~yuning/subnets/TIGAswp.kml "TIGAswp.kml"]</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Subnets_GoogleEarth&diff=611 Subnets GoogleEarth 2008-07-30T19:56:50Z

<p>Yuning: </p> <hr /> <div>The ".kml" files have been edit for ''Google Earth'', then you can "open" these files with ''Goolge Earth'' and play around with them.<br /> <br /> Download ".kml" files here:<br /> <br /> Alaska: [http://gps.alaska.edu/~yuning/subnets/Alaska.kml "Alaska.kml"]<br /> <br /> [[Image:http://gps.alaska.edu/~yuning/subnets/Alaska.jpg "asd"]]<br /> <br /> CASA: [http://gps.alaska.edu/~yuning/subnets/CASA.kml "CASA.kml"]<br /> <br /> EurAf: [http://gps.alaska.edu/~yuning/subnets/EurAf.kml "EurAf.kml"]<br /> <br /> Greenland: [http://gps.alaska.edu/~yuning/subnets/Greenland.kml "Greenland.kml"]<br /> <br /> NCal: [http://gps.alaska.edu/~yuning/subnets/NCal.kml "NCal.kml"]<br /> <br /> NEAsia: [http://gps.alaska.edu/~yuning/subnets/NEAsia.kml "NEAsia.kml"]<br /> <br /> NOAM: [http://gps.alaska.edu/~yuning/subnets/NOAM.kml "NOAM.kml"]<br /> <br /> Tibet: [http://gps.alaska.edu/~yuning/subnets/Tibet.kml "Tibet.kml"]<br /> <br /> TIGAswp: [http://gps.alaska.edu/~yuning/subnets/TIGAswp.kml "TIGAswp.kml"]</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Subnets_GoogleEarth&diff=610 Subnets GoogleEarth 2008-07-30T19:55:56Z

<p>Yuning: </p> <hr /> <div>The ".kml" files have been edit for ''Google Earth'', then you can "open" these files with ''Goolge Earth'' and play around with them.<br /> <br /> Download ".kml" files here:<br /> <br /> Alaska: [http://gps.alaska.edu/~yuning/subnets/Alaska.kml "Alaska.kml"]<br /> <br /> [[Image:Example.jpg]]<br /> <br /> CASA: [http://gps.alaska.edu/~yuning/subnets/CASA.kml "CASA.kml"]<br /> <br /> EurAf: [http://gps.alaska.edu/~yuning/subnets/EurAf.kml "EurAf.kml"]<br /> <br /> Greenland: [http://gps.alaska.edu/~yuning/subnets/Greenland.kml "Greenland.kml"]<br /> <br /> NCal: [http://gps.alaska.edu/~yuning/subnets/NCal.kml "NCal.kml"]<br /> <br /> NEAsia: [http://gps.alaska.edu/~yuning/subnets/NEAsia.kml "NEAsia.kml"]<br /> <br /> NOAM: [http://gps.alaska.edu/~yuning/subnets/NOAM.kml "NOAM.kml"]<br /> <br /> Tibet: [http://gps.alaska.edu/~yuning/subnets/Tibet.kml "Tibet.kml"]<br /> <br /> TIGAswp: [http://gps.alaska.edu/~yuning/subnets/TIGAswp.kml "TIGAswp.kml"]</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Subnets_GoogleEarth&diff=609 Subnets GoogleEarth 2008-07-30T19:26:47Z

<p>Yuning: </p> <hr /> <div>The ".kml" files have been edit for ''Google Earth'', then you can "open" these files with ''Goolge Earth'' and play around with them.<br /> <br /> Download ".kml" files here:<br /> <br /> Alaska: [http://gps.alaska.edu/~yuning/subnets/Alaska.kml "Alaska.kml"]<br /> <br /> CASA: [http://gps.alaska.edu/~yuning/subnets/CASA.kml "CASA.kml"]<br /> <br /> EurAf: [http://gps.alaska.edu/~yuning/subnets/EurAf.kml "EurAf.kml"]<br /> <br /> Greenland: [http://gps.alaska.edu/~yuning/subnets/Greenland.kml "Greenland.kml"]<br /> <br /> NCal: [http://gps.alaska.edu/~yuning/subnets/NCal.kml "NCal.kml"]<br /> <br /> NEAsia: [http://gps.alaska.edu/~yuning/subnets/NEAsia.kml "NEAsia.kml"]<br /> <br /> NOAM: [http://gps.alaska.edu/~yuning/subnets/NOAM.kml "NOAM.kml"]<br /> <br /> Tibet: [http://gps.alaska.edu/~yuning/subnets/Tibet.kml "Tibet.kml"]<br /> <br /> TIGAswp: [http://gps.alaska.edu/~yuning/subnets/TIGAswp.kml "TIGAswp.kml"]</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Subnets_GoogleEarth&diff=608 Subnets GoogleEarth 2008-07-30T19:26:26Z

<p>Yuning: </p> <hr /> <div>The ".kml" files have been edit for ''Google Earth'', then you can "open" these files with ''Goolge Earth'' and play around with them.<br /> <br /> Download ".kml" files here:<br /> <br /> Alaska: [http://gps.alaska.edu/~yuning/subnets/Alaska.kml "Alaska.kml"]<br /> CASA: [http://gps.alaska.edu/~yuning/subnets/CASA.kml "CASA.kml"]<br /> EurAf: [http://gps.alaska.edu/~yuning/subnets/EurAf.kml "EurAf.kml"]<br /> Greenland: [http://gps.alaska.edu/~yuning/subnets/Greenland.kml "Greenland.kml"]<br /> NCal: [http://gps.alaska.edu/~yuning/subnets/NCal.kml "NCal.kml"]<br /> NEAsia: [http://gps.alaska.edu/~yuning/subnets/NEAsia.kml "NEAsia.kml"]<br /> NOAM: [http://gps.alaska.edu/~yuning/subnets/NOAM.kml "NOAM.kml"]<br /> Tibet: [http://gps.alaska.edu/~yuning/subnets/Tibet.kml "Tibet.kml"]<br /> TIGAswp: [http://gps.alaska.edu/~yuning/subnets/TIGAswp.kml "TIGAswp.kml"]</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Subnets_GoogleEarth&diff=607 Subnets GoogleEarth 2008-07-30T19:16:48Z

<p>Yuning: </p> <hr /> <div>The ".kml" files have been edit for ''Google Earth'', then you can "open" these files with ''Goolge Earth'' and play around with them.<br /> <br /> [[Image:http://gps.alaska.edu/~yuning/subnets/Alaska.jpg]]</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Subnets&diff=620 Subnets 2008-07-30T19:06:41Z

<p>Yuning: </p> <hr /> <div>We have several (sub)networks, which enables us to process the solution of a certain set of stations without conflicting the limits set by computer resources.<br /> <br /> Those subnets are: <br /> <br /> {|<br /> !align="left" !width="100" | name || !width="200" | where || !width="50" | map <br /> |- <br /> | alaska <br /> | align="center" | Alaska region<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/Alaska.subnet.pdf alaska]<br /> |-<br /> | casa <br /> | align="center" | South America<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/CASA.subnet.pdf casa]<br /> |-<br /> | TIGAswp <br /> | align="center" | South-West Alaska<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/TIGAswp.subnet.pdf TIGAswp]<br /> |-<br /> | tibet<br /> |<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/Tibet.subnet.pdf tibet]<br /> |-<br /> | NEAsia<br /> | align="center" | North-East Asia<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/NEAsia.subnet.pdf NEAsia]<br /> |-<br /> | NOAM<br /> | align="center" | North America<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/NOAM.subnet.pdf NOAM]<br /> <br /> |}<br /> <br /> <br /> To see a plot for each subnet click on the subnet name under "map".<br /> <br /> You can also look at our subnets using Google Earth (see [[subnets_GoogleEarth|here]]).</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Subnets_gooleearht&diff=1600 Subnets gooleearht 2008-07-30T19:04:54Z

<p>Yuning: </p> <hr /> <div>[[Image:E:\GPS\subnets\alaska.jpg]]</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Subnets_gooleearht&diff=605 Subnets gooleearht 2008-07-30T19:02:59Z

<p>Yuning: </p> <hr /> <div>[[Image:alaska.jpg]]</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Subnets&diff=606 Subnets 2008-07-30T18:57:43Z

<p>Yuning: </p> <hr /> <div>We have several (sub)networks, which enables us to process the solution of a certain set of stations without conflicting the limits set by computer resources.<br /> <br /> Those subnets are: <br /> <br /> {|<br /> !align="left" !width="100" | name || !width="200" | where || !width="50" | map <br /> |- <br /> | alaska <br /> | align="center" | Alaska region<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/Alaska.subnet.pdf alaska]<br /> |-<br /> | casa <br /> | align="center" | South America<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/CASA.subnet.pdf casa]<br /> |-<br /> | TIGAswp <br /> | align="center" | South-West Alaska<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/TIGAswp.subnet.pdf TIGAswp]<br /> |-<br /> | tibet<br /> |<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/Tibet.subnet.pdf tibet]<br /> |-<br /> | NEAsia<br /> | align="center" | North-East Asia<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/NEAsia.subnet.pdf NEAsia]<br /> |-<br /> | NOAM<br /> | align="center" | North America<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/NOAM.subnet.pdf NOAM]<br /> <br /> |}<br /> <br /> <br /> To see a plot for each subnet click on the subnet name under "map".<br /> <br /> You can also look at our subnets using Google Earth (see [[subnets_gooleearht|here]]).</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Subnets&diff=604 Subnets 2008-07-30T18:56:59Z

<p>Yuning: </p> <hr /> <div>We have several (sub)networks, which enables us to process the solution of a certain set of stations without conflicting the limits set by computer resources.<br /> <br /> Those subnets are: <br /> <br /> {|<br /> !align="left" !width="100" | name || !width="200" | where || !width="50" | map <br /> |- <br /> | alaska <br /> | align="center" | Alaska region<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/Alaska.subnet.pdf alaska]<br /> |-<br /> | casa <br /> | align="center" | South America<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/CASA.subnet.pdf casa]<br /> |-<br /> | TIGAswp <br /> | align="center" | South-West Alaska<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/TIGAswp.subnet.pdf TIGAswp]<br /> |-<br /> | tibet<br /> |<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/Tibet.subnet.pdf tibet]<br /> |-<br /> | NEAsia<br /> | align="center" | North-East Asia<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/NEAsia.subnet.pdf NEAsia]<br /> |-<br /> | NOAM<br /> | align="center" | North America<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/NOAM.subnet.pdf NOAM]<br /> <br /> |}<br /> <br /> <br /> To see a plot for each subnet click on the subnet name under "map".<br /> <br /> You can also look at our subnets using Google Earth [[subnets_gooleearht|here]].</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Subnets&diff=603 Subnets 2008-07-30T18:53:52Z

<p>Yuning: </p> <hr /> <div>We have several (sub)networks, which enables us to process the solution of a certain set of stations without conflicting the limits set by computer resources.<br /> <br /> Those subnets are: <br /> <br /> {|<br /> !align="left" !width="100" | name || !width="200" | where || !width="50" | map <br /> |- <br /> | alaska <br /> | align="center" | Alaska region<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/Alaska.subnet.pdf alaska]<br /> |-<br /> | casa <br /> | align="center" | South America<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/CASA.subnet.pdf casa]<br /> |-<br /> | TIGAswp <br /> | align="center" | South-West Alaska<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/TIGAswp.subnet.pdf TIGAswp]<br /> |-<br /> | tibet<br /> |<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/Tibet.subnet.pdf tibet]<br /> |-<br /> | NEAsia<br /> | align="center" | North-East Asia<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/NEAsia.subnet.pdf NEAsia]<br /> |-<br /> | NOAM<br /> | align="center" | North America<br /> | align="center" | [http://www.gps.alaska.edu/tfour/Misc/subnets/NOAM.subnet.pdf NOAM]<br /> <br /> |}<br /> <br /> <br /> To see a plot for each subnet click on the subnet name under "map".<br /> <br /> You can also look at our subnets using Google Earth (see here).</div>

Yuning http://gps.alaska.edu/internal/index.php?title=WHOS&diff=623 WHOS 2008-07-29T19:32:20Z

<p>Yuning: /* Week Schedule as of 9/7/07 */</p> <hr /> <div>The WHOS list tracks assigned GPS weeks for processing.<br /> <br /> More details about analysis at [[GPS analysis system]].<br /> <br /> ===Recent weeks===<br /> <pre><br /> week # start date last processed who status<br /> ****************************************************************<br /> 1375 05/14/2006 Trivikram/trivikram 1/ CLEAN EXCEPT 2 DAYS<br /> 1376 05/21/2006 Trivikram/1-2/ CLEAN<br /> 1377 05/28/2006 07/20/2006 Trivikram 1<br /> 1378 06/04/2006 07/20/2006 Trivikram 1 <br /> 1379 06/11/2006 07/20/2006 Trivikram 1 <br /> 1380 06/18/2006 07/20/2006 Trivikram 1 <br /> 1381 06/25/2006 07/12/2006 Ryan<br /> 1382 07/02/2006 Julie<br /> 1383 07/09/2006 Julie<br /> 1384 07/16/2006 Julie<br /> 1385 07/23/2006 Julie<br /> <br /> 1413 02/04/2007 05/01/2007 Tom<br /> </pre><br /> ===Week Schedule as of 9/7/07===<br /> <pre><br /> week # start date last processed who status<br /> *************************************************************<br /> 1430 Brandon NEAsia Alaska and NOAM-clean<br /> <br /> 1431 09/??/2007 10/31/2007 Lissy AK - clean<br /> 1431 11/05/2007 01/??/2008 Lissy initial cleaning done for Tibet solution<br /> 1431 01/09/2008 Lissy Casa solutions started<br /> <br /> 1432 Yuning initial cleaning done<br /> 1433 09/14/2007 09/26/2007 Ronni 1st iteration <br /> 1434 Julie<br /> 1435 Julie<br /> 1436 Julie<br /> 1437 Julie<br /> 1438 Julie<br /> 1439 Brandon one more iteration<br /> 1440 12?/??/2007 Lissy<br /> 1441 Yuning initial cleaning done<br /> 1442 09/27/2007 Ronni initial cleaning done<br /> 1443 Brandon NEA clean<br /> 1444 01/16/2008 Lissy<br /> 1445 Yuning initial cleaning done<br /> 1446 03/11/2008 Ronni<br /> 1447 Brandon initial cleaning done<br /> 1448 11/16/2007 05/12/2008 Lissy initial cleaning done<br /> 1449 Brandon NEA and Alaska cleaned<br /> 1450 Brandon initial cleaning done<br /> 1451 Brandon initial cleaning done<br /> 1452 01/23/2008 01/28/2008 Lissy initial cleaning done for Tibet & casa solution <br /> 1453 Yuning initial cleaning done<br /> 1454 05/05/2008 Ronni AK first interation<br /> 1455 Brandon initial cleaning done<br /> 1456 01/28/2008 Lissy<br /> 1457 Yuning initial cleaning done<br /> 1458 05/05/2008 Ronni AK first interation<br /> 1459 Julie<br /> 1460 Brandon NEA and AK cleaned<br /> 1461 02/06/2008 Lissy<br /> 1462 Yuning initial cleaning done<br /> 1463 05/05/2008 Ronni AK first interation<br /> 1464 Julie<br /> 1465 Brandon initial cleaning done<br /> 1466 04/09/2008 Lissy<br /> 1467 Yuning initial cleaning done<br /> 1468 05/05/2008 Ronni AK first interation<br /> 1469 Julie<br /> 1470 Brandon initial cleaning done<br /> 1471 04/09/2008 Lissy<br /> 1472 Yuning AK cleaning done<br /> 1473 05/05/2008 Ronni AK first interation<br /> 1474 Julie<br /> 1475 Brandon<br /> 1476 Lissy<br /> 1477 Yuning AK cleaning done<br /> 1478 05/05/2008 Ronni AK first interation<br /> 1479 Julie<br /> 1480 Brandon<br /> 1481 Lissy<br /> 1482 Yuning<br /> 1483 Ronni<br /> 1484 Julie<br /> 1485 Brandon<br /> 1486 Lissy<br /> 1487 Yuning<br /> 1488 Ronni<br /> 1489 Julie<br /> 1490 Brandon<br /> 1491 Lissy<br /> 1492 Yuning<br /> 1493 Ronni<br /> 1494 Julie<br /> 1495 Brandon<br /> 1496 Lissy<br /> 1497 Yuning<br /> 1498 Ronni<br /> 1499 Julie<br /> 1500 Brandon<br /> <br /> </pre><br /> <br /> ===2006===<br /> <pre><br /> week # start date last processed who status<br /> ****************************************************************<br /> 1357 01/08/2006 Sandeep CLEANING Venkat<br /> 1358 01/15/2006 Sandeep CLEANING Venkat<br /> 1359 01/22/2006 Sandeep CLEAN Venkat (AK Point File Size < 300)<br /> 1360 01/29/2006 Sandeep CLEANING Venkat<br /> 1361 02/05/2006 Trivikram<br /> 1362 02/12/2006 Trivikram CLEAN (AK Point file size < 400)<br /> 1363 02/19/2006 Venkat CLEAN (AK Point file size < 400)<br /> 1364 02/26/2006 Trivikram<br /> 1365 03/05/2006 Venkat CLEANING <br /> 1366 03/12/2006 Trivikram<br /> 1367 03/19/2006 Trivikram <br /> 1368 03/26/2006 Trivikram problem with AK CLEANING SOLN<br /> 1369 04/02/2006 Trivikram CLEAN<br /> 1370 04/09/2006 Tom <br /> 1371 04/16/2006 Venkat CLEANING<br /> 1372 04/23/2006 Venkat CLEANING <br /> 1373 04/30/2006 Venkat CLEANING<br /> 1374 05/07/2006 Venkat CLEANING<br /> </pre><br /> <br /> ===2005===<br /> <pre><br /> week # start date last processed who status<br /> ****************************************************************<br /> 1304 01/02/2005 09/16/2005 Ryan CLEAN<br /> 1305 01/09/2005 08/30/2005 Pravee CLEAN<br /> 1306 01/16/2005 07/15/2005 Jill WORKING Trivikram(tibet) 07/26/2006 CLEAN<br /> 1307 01/23/2005 08/31/2005 Pravee CLEAN Trivikram(tibet) 07/26/2006 CLEAN<br /> 1308 01/30/2005 04/05/2005 Jill CLEAN Trivikram(tibet) 07/26/2006 CLEAN<br /> 1309 02/06/2005 08/31/2005 Pravee CLEAN <br /> 1310 02/13/2005 03/12/2005 Julie CLEAN <br /> 1311 02/20/2005 03/12/2005 Pravee CLEANING<br /> 1312 02/27/2005 03/31/2005 Tom CLEAN<br /> 1313 03/06/2005 03/31/2005 Pravee CLEANING<br /> 1314 03/13/2005 03/31/2005 Tom CLEAN<br /> 1315 03/20/2005 06/13/2005 Samik CLEAN (Point File Size < 500)<br /> 1316 03/27/2005 06/13/2005 Samik CLEAN (Point File Size < 400) <br /> 1317 04/03/2005 06/16/2005 Samik CLEAN (Point File Size < 400)<br /> 1318 04/10/2005 9/15/2005 Ryan not sure what's going on?<br /> 1319 04/17/2005 10/4/2005 Ryan ak SUBMITTED<br /> 1320 04/24/2005 Sandeep Done 1 2 Trivikram(tibet) 07/27/2006 1 2 CLEAN except 2 days<br /> 1321 05/01/2005 Sandeep Done 1 2 Trivikram(tibet) 07/28/2006 1 <br /> 1322 05/08/2005 Sandeep Done 1 2 Trivikram(tibet) 07/28/2006 1<br /> 1323 05/15/2005 Sandeep Done 1 2 Trivikram(tibet) 08/04/2006 1 <br /> 1324 05/22/2005 Sandeep Done 1 2 Trivikram(tibet) 08/04/2006 1<br /> 1325 05/29/2005 Sigrun DONE Trivikram(tibet) 08/04/2006 1<br /> 1326 06/05/2005 Sigrun DONE Trivikram(tibet) 08/06/2006 1<br /> 1327 06/12/2005 Sandeep Done 1 2 NO TIBET<br /> 1328 06/19/2005 Sandeep Done 1 2 No TIBET<br /> 1329 06/26/2005 Sandeep Done 1 2 Trivikram(tibet) 08/18/2006 1<br /> 1330 07/03/2005 9/14/2005 Ryan DONE<br /> 1331 07/10/2005 11/10/2005 Tom Submitted<br /> 1332 07/17/2005 Sandeep CLEAN Venkat (AK Point File Size < 500)<br /> 1333 07/24/2005 Sandeep CLEAN Trivikram <br /> 1334 07/31/2005 Sandeep CLEAN Trivikram <br /> 1335 08/07/2005 9/12/2005 Tom CLEAN Venkat (AK Point File Size < 400)<br /> 1336 08/14/2005 Sandeep CLEAN Venkat (AK Point File Size < 300)<br /> 1337 08/21/2005 10/17/2005 Ryan ak CLEAN Venkat (AK Point File Size < 300) <br /> 1338 08/28/2005 10/17/2005 Ryan ak CLEAN Venkat (AK Point File Size < 300) <br /> 1339 09/04/2005 11/08/2005 Ryan CLEAN Trivikram (AK Point File Size < 300) <br /> 1340 09/11/2005 Sandeep CLEAN Venkat (AK Point File Size < 300)<br /> 1341 09/18/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1342 09/25/2005 Sandeep CLEAN Venkat (AK Point File Size < 300) <br /> 1343 10/02/2005 Sandeep CLEAN Venkat (AK Point File Size < 300)<br /> 1344 10/09/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1345 10/16/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1346 10/23/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1347 10/30/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1348 11/06/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1349 11/13/2005 Sandeep CLEAN Venkat (AK Point File Size < 300) <br /> 1350 11/20/2005 Sandeep CLEAN Venkat (AK Point File Size < 400) <br /> 1351 11/27/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1352 12/04/2005 Sandeep CLEAN Venkat (AK Point File Size < 300) <br /> 1353 12/11/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1354 12/18/2005 Sandeep CLEANING Venkat<br /> 1356 12/25/2005 Sandeep CLEANING Venkat<br /> </pre><br /> <br /> ===Older Stuff===<br /> <pre><br /> week # start date last processed who status<br /> ****************************************************************<br /> ****************************************************************<br /> ***************************2002*********************************<br /> **************************EARTHQUAKE****************************<br /> 1189 10/20/02 02/26/05 Josh PENDING<br /> 1190 10/27/02 Josh PENDING<br /> 1191 11/03/02 03/04/05 Josh DONE<br /> 1192 11/10/02 03/11/05 Josh DONE<br /> 1193 11/17/02 03/11/05 Josh DONE<br /> 1194 11/24/02 03/11/05 Josh DONE<br /> 1195 12/01/02 03/11/05 Josh RUNNING<br /> 1196 12/08/02 03/11/05 Josh DONE<br /> 1197 12/15/02 03/11/05 Josh DONE<br /> 1198 12/22/02 03/12/05 Josh DONE<br /> 1199 12/29/02 03/12/05 Josh DONE<br /> <br /> *************************2003***********************************<br /> <br /> 1200 01/05/03 03/12/05 Josh DONE<br /> 1201 01/12/03 03/12/05 Josh DONE<br /> 1202 01/19/03 03/15/05 Josh RUNNING<br /> 1203 01/26/03 03/14/05 Josh DONE<br /> 1204 02/02/03 03/14/05 Josh DONE<br /> 1205 02/09/03 Josh PENDING<br /> 1206 02/16/03 Josh PENDING<br /> 1207 02/23/03 Josh PENDING<br /> 1208 03/02/03 02/26/05 Josh ALMOST CLEAN<br /> 1209 03/09/03 02/26/05 Josh ALMOST CLEAN<br /> 1210 03/16/03 02/26/05 Josh NEEDS CLEAN<br /> 1211 03/23/03 02/27/05 Josh DONE<br /> 1212 03/30/03 02/26/05 Josh DONE<br /> 1213 04/06/03 03/12/05 Josh RUNNING<br /> 1214 04/13/03 02/26/05 Josh CLEANED<br /> 1215 04/20/03 02/27/05 Josh CLEANED<br /> 1216 04/27/03 02/26/05 Josh PENDING<br /> 1217 05/04/03 02/26/05 Josh NEEDS CLEAN<br /> 1218 05/11/03 02/27/05 Josh NEEDS CLEAN<br /> 1219 05/18/03 02/27/05 Josh WORKING<br /> 1220 05/25/03 02/27/05 Josh PENDING<br /> 1221 06/01/03 Josh PENDING<br /> 1222 06/08/03 Josh PENDING<br /> 1223 06/15/03 Josh PENDING<br /> 1224 06/22/03 Josh PENDING<br /> 1225 06/29/03 02/26/05 Josh FAILED<br /> 1226 07/06/03 02/26/05 Josh ALMOST CLEAN<br /> 1227 07/13/03 02/26/05 Josh FAILED<br /> 1228 07/20/03 Josh FAILED<br /> 1229 07/27/03 11/10/05 Tom Submitted <br /> 1230 08/03/03 Josh FAILED<br /> 1231 08/10/03 Josh FAILED<br /> 1232 08/17/03 11/10/05 Tom Submitted <br /> 1233 08/24/03 02/26/05 Josh ALMOST CLEAN<br /> 1234 08/31/03 02/26/05 Josh ALMOST CLEAN<br /> 1235 09/07/03 02/26/05 Josh ALMOST CLEAN<br /> 1236 09/14/03 02/26/05 Josh ALMOST CLEAN<br /> 1237 09/21/03 02/26/05 Josh NEEDS CLEAN<br /> 1238 09/28/03 02/26/05 Josh NEEDS CLEAN<br /> 1239 10/05/03 02/26/05 Josh WORKING<br /> 1240 10/12/03 02/26/05 Josh PENDING<br /> 1241 10/19/03 02/26/05 Josh NEEDS CLEAN<br /> 1242 10/26/03 02/26/05 Josh ALMOST CLEAN<br /> 1243 11/02/03 02/26/05 Josh NEEDS CLEAN<br /> 1244 11/09/03 02/26/05 Josh NEEDS CLEAN<br /> 1245 11/16/03 02/26/05 Josh ALMOST CLEAN<br /> 1246 11/23/03 02/26/05 Josh ALMOST CLEAN<br /> 1247 11/30/03 02/26/05 Josh ALMOST CLEAN<br /> 1248 12/07/03 02/26/05 Josh NEEDS CLEAN<br /> 1249 12/14/03 02/26/05 Josh NEEDS CLEAN<br /> 1250 12/21/03 02/26/05 Josh NEEDS CLEAN<br /> 1251 12/28/03 02/26/05 Josh WORKING<br /> <br /> ***************************2004*********************************<br /> <br /> 1253 01/11/04 02/26/05 Josh PENDING<br /> 1254 01/18/04 Josh PENDING<br /> 1255 01/25/04 Josh NEEDS<br /> 1256 02/01/04 Josh PENDING<br /> 1257 02/08/04 Josh PENDING<br /> 1258 02/15/04 Josh PENDING<br /> 1259 02/22/04 Josh PENDING<br /> 1260 02/29/04 Josh PENDING<br /> 1261 03/07/04 02/26/05 Josh PENDING<br /> 1262 03/14/04 02/26/05 Josh NEEDS CLEAN<br /> 1263 03/21/04 02/26/05 Josh NEEDS CLEAN<br /> 1264 03/28/04 02/26/05 Josh NEEDS CLEAN<br /> 1265 04/04/04 02/26/05 Josh FAILED No files found, needs re<br /> run<br /> 1266 04/11/04 02/26/05 Josh FAILED No files found, needs re<br /> run<br /> 1267 04/18/04 02/26/05 Josh NEEDS CLEAN<br /> 1268 04/25/04 02/26/05 Josh NEEDS CLEAN<br /> 1269 05/02/04 02/26/05 Josh NEEDS CLEAN<br /> 1270 05/09/04 02/26/05 Josh NEEDS CLEAN<br /> 1271 05/16/04 02/26/05 Josh NEEDS CLEAN<br /> 1272 05/23/04 02/26/05 Josh NEEDS CLEAN<br /> 1273 05/30/04 02/26/05 Josh NEEDS CLEAN<br /> 1274 06/06/04 02/26/05 Josh NEEDS CLEAN<br /> 1275 06/13/04 02/26/05 Josh NEEDS CLEAN<br /> 1276 06/20/04 02/27/05 Samik DONE<br /> 1277 06/27/04 03/19/05 Jeff NEEDS CLEAN<br /> 1278 07/04/04 03/19/05 Jeff NEEDS CLEAN<br /> 1279 07/11/04 03/19/05 Jeff NEEDS CLEAN<br /> 1280 07/18/04 03/19/05 Jeff NEEDS CLEAN<br /> 1281 07/25/04 03/19/05 Jeff NEEDS CLEAN<br /> 1282 08/01/04 Josh PENDING<br /> 1283 08/08/04 Josh PENDING<br /> 1284 08/15/04 Josh PENDING<br /> 1285 08/22/04 Josh PENDING<br /> 1286 08/29/04 Josh PENDING<br /> 1287 09/05/04 Josh PENDING<br /> 1288 09/12/04 Josh PENDING<br /> 1289 09/19/04 03/19/05 Jeff ??<br /> 1290 09/26/04 Josh PENDING<br /> 1291 10/03/04 Josh PENDING<br /> 1292 10/10/04 03/19/05 Jeff ??<br /> 1293 10/17/04 Josh PENDING<br /> 1294 10/24/04 03/19/05 Jeff ??<br /> 1295 10/31/04 03/25/05 Tom CLEAN<br /> 1296 11/07/04 04/07/05 Tom Cleaning<br /> 1297 11/14/04 03/19/05 Jeff ??<br /> 1298 11/21/04 NEEDS CLEAN<br /> 1299 11/28/04 NEEDS CLEAN<br /> 1300 12/05/04 08/16/05 Pravee CLEAN<br /> 1301 12/12/04 08/19/05 Pravee CLEAN<br /> 1302 12/19/04 08/19/05 Pravee CLEAN trivikram(tibet) CLEAN 07/26/2006<br /> 1303 12/26/04 08/26/05 Pravee CLEAN <br /> </pre><br /> <br /> ===Archaic (pre-1996)===<br /> <pre><br /> week # start date last processed who status<br /> ****************************************************************<br /> At the moment, Jeff is dealing with these.<br /> </pre></div>

Yuning http://gps.alaska.edu/internal/index.php?title=Fieldwork&diff=1564 Fieldwork 2008-07-28T20:00:32Z

<p>Yuning: </p> <hr /> <div>:''Reach site, hunt around,''<br /> :''Setup, precise centering,''<br /> :''Yellow box takes data.''<br /> ::''- A concise guide to GPS fieldwork''<br /> <br /> Perhaps the most important thing to remember about GPS fieldwork is that with a 24-hour GPS survey you can measure the position of the GPS antenna to within about 2 mm horizontal precision and 6 mm vertical precision, and you can measure the vector between two GPS antennas even more precisely than that. What this means is that the tolerances for setup error are very tight and you have to be very careful. If not, YOU are likely to be the limiting error source in the measurements. It also means that you really can't hide it if you screw up. So do your best if you make a mistake or something odd happens, carefully record it on the log sheet. It is far better to know we have a bad observation than to find out years later.<br /> <br /> ===Where can I find site information?===<br /> We maintain a [http://gps.alaska.edu/gps GPS Site Database] that in theory stores site information from all the GPS sites we use. In practice, some are missing, but the database is mostly complete for Alaska and environs. You can search the database by 4 characeter ID, or radial or rectangular searches, and other ways as well. To access the database, you need a login and password, and for that you need to ask Jeff.<br /> <br /> ===Traveling in Alaska===<br /> <br /> Before you go on official University travel be sure to fill out a Travel Authorization (TA) form. You can get this from Candice Lake on the 6th floor in the buisness office. Even if you do not expect to spend money on the trip, it is important that you fill out this form for insurance purposes. When you return it is necessary to fill out an expense report (to be sure you are reimbursed for incurred costs), even if you had no expenses.<br /> <br /> <b>Rental Cars</b><br><br /> A rental is often the cheapest way to travel on the road network in Alaska. If you are traveling on University buisness (fieldwork falls in this <br /> category) then the university covers the insurance, be sure to decline coverage when renting the car. Be sure to print [http://gps.alaska.edu/tfour/Misc/travel_papers.pdf this document] when traveling in a rental car; it contains [http://gps.alaska.edu/tfour/Misc/travel_papers.pdf proof of insurance] and some phone numbers to call if an accident occurs. The GI recommends that you '''not''' rent from Budget due to their aggressive collection agency should damages occur to the vehicle while in your possesion. The GI recommends using [http://www.avis.com Avis] or some other rental company. Do not rent from the airport rental location, there is an additional 10% tax plus fees added to the price of rental if you rent from the airport. Most of the rental companies have other locations in town, which have lower costs. <br /> <br /> <b>Flying in the Bush</b><br><br /> This is not your regular commercial flight, get all the information you need prior to departure.<br /> <br /> ===How to set up a tripod===<br /> <br /> There are as many different explanations as people who have set up a tripod before. Well, one description you can use is this: Follow the link to a printable [http://www.gps.alaska.edu/tfour/Misc/tripodsetup1.pdf setup description] and/or the link to [[new site and tripod setup description]].<br /> <br /> ===How to set up a spike mount===<br /> 1) Locate benchmark with hand-held GPS or site description.<br /> <br /> 2) Assemble spike mount by attaching legs to spike.<br /> a. *Out of the case the legs on the spike mount will be short. Use the leg extensions as needed to improve stability.<br /> b. Additional wing-nuts, lock washers and spike tips are included in the case<br /> 3) Set the spike on the benchmark with the legs oriented at 90 degrees from each other, or as close to 90 as possible.<br /> <br /> 4) Loosely tighten the wing-nut on the leg extensions to hold the leg lengths.<br /> <br /> 5) Use the carpenter’s level and the leg screws to level each leg independently.<br /> <br /> 6) Loosen the wing nuts and add weights (rocks) to hold the leg positions, retighten the wing nuts.<br /> <br /> 7) Attach the leveling plate to the spike and place the bull’s-eye level on the plate.<br /> <br /> 8) Use the leg screw to level the plate. Once the plate is level tighten the locking nut on the legs.<br /> <br /> 9) Remove the leveling plate.<br /> <br /> 10) Attach the antenna to the spike. ** Do not attach the antenna cable yet.**<br /> a. Make sure at least one spike clamp is tight, to ensure that the spike doesn’t rotate when tightening the antenna.<br /> 11) Orient the antenna to north.<br /> a. Set the declination on your compass, the compass can be placed directly onto the antenna. <br /> b. Some antennas are marked with a North arrow others are not. If there is no North direction indicated, Notch 1 <br /> (located at the edge on the antenna) should be pointed north.<br /> c. The antenna will likely need to be rotated. Loosen the spike clamps and rotate in the clockwise (tightening)<br /> direction.<br /> 12) Hook the receiver up to power.<br /> <br /> 13) Attach the antenna cable to receiver and antenna.<br /> <br /> ===Orienting the antenna to TRUE NORTH===<br /> Every antenna has a reference line or arrow that must be oriented toward TRUE NORTH. The reason for this is that the position actually measured by GPS is something called the ''antenna phase center'', which in general is not located on the axis of the antenna. So if you orient the antenna in some other direction, you introduce an error into the resulting postion that for many antennas is much larger than the measurement uncertainty.<br /> :The reference arrow for the Trimble 4000's antenna is marked on the antenna.<br /> :For other antennas, the antenna cable connector should point to NORTH. There will normally be something marked on the top of the antenna along that same line.<br /> <br /> To orient the antenna, you need to know the magnetic declination. It should be recorded on the site description. If not, it can be found on any USGS topo map. If all else fails, remember 25 degrees east, which is not too far off for most of central and southern Alaska.<br /> :If the declination is EAST, set your compass to 360 - declination and orient by the north arrow on the compass.<br /> :If the declination is WEST, set your compass to 360 + declination and orient by the north arrow on the compass.<br /> <br /> If you find that you oriented the antenna the wrong way, and it is already recording data, don't do anything rash! The best thing to do in this case is to carefully record the actual orientation of the antenna. <br /> <br /> ===Programming a Trimble 4000 receiver===<br /> You can find a printable description of a [http://www.gps.alaska.edu/tfour/Misc/ReceiverSetup_multiday.pdf multi-day receiver setup] by clicking on that link.<br /> <br /> ===Using the Trimble 5700 and R7 receivers===<br /> These two receivers are basically the same thing. Neither one is convenient to program in the field. Turn them on and they should work.<br /> <br /> What the lights mean.<br /> <br /> <br /> ===Using the Trimble Net-RS receiver===<br /> <br /> The main issue with the Net-RS receiver is that it writes all data for one UTC day into ONE file. This must be<br /> considered when a station is moved within one UTC day between sites. It is possible to untangle the data but still it's a hassle. In Alaska a new UTC day starts at 4:00 pm, meaning that taking the station down before 4 pm and setting it out somewhere else after 4 pm would be ideal.<br /> <br /> If you must visit 2 sites on the same Julian day, here is a way to get the data to go into separate files. You'll need a laptop, and a crossover (Xover) ethernet cable. Set your network settings on the laptop to IP: 192.168.1.3 NetMask: 255.255.255.0 Gateway: 192.168.1.1<br /> Connect the laptop to the NetRS. Open internet explorer or equiv. and go to the site 192.168.1.2<br /> The web interface should appear with a blue background. Under Data Logging, switch from one 30sec 24hour session to another by toggling the appropriate "enable" boxes. If you need to program a second campaign session, read the manual.<br /> <br /> ATTN: The Net-RS receiver has different power and antenna inputs! Make sure you have the right cables (usually they do not fit into the black case) before you leave the vehicle, especially when the site is away from the road.<br /> <br /> ===Using the Topcon GB-1000 receiver===<br /> There is printable introduction here: [http://gps.alaska.edu/~yuning/topcongb1000.pdf Topcon Guide]<br /> <br /> ===Downloading the Trimble 4000 receiver===<br /> <br /> <br /> ===Downloading the Trimble 5700 receiver===<br /> <br /> We will use the "Windows system" computer to download data from Trimber 5700 receiver. And also make sure that log sheet is at your hand.<br /> <br /> 1. Take the Trimble 5700 receiver out from the yellow box (I know it's "crap", but it's exact what we do first).<br /> <br /> 2. There are two cables needed to plug into the receiver: power cable (circle); data cable (a little bit rectangular). Power on the receiver.<br /> <br /> 3. Double click "Shortcut to DataXfer.exe" on the computer desktop. If the receiver is already connected, the software will display the receiver and its series number, check the number and what was recorded on the log sheet, make sure they are matched.<br /> <br /> 4. Click the "add" button, then you can see all the recorded data in the receiver. Choose the data you want to download, and make sure save the data file to directory E:\GPSdata\. For example, if we want to download compaign data of KENAI trip in 2008, the subdirectory can be created as E:\GPSdata\data 2008\campaign\kenai, and the downloaded data should go to there. Then, click "Transfer", then you will see the computer doing its work to download data. And you need to click "OK" during the download.<br /> <br /> 5. Change files name. Usually, there are two files for one day of one site: *.dat and *.T00. Change the first 4 letters to site name for both of these two files. For example, for site DAHL, the data file name should be changed to the format like this: "dahl1430.dat" and "dahl1430.T00" (143 is the Julian day). If the name of site has only 3 letters (site CPR, for example), then names should be like this: "cpr_1450.dat" and "cpr_1450.T01". <br /> <br /> 6. The download work is done. Power off receiver and put the receiver back to the yellow box. Check if all the stuff (receiver, antenna, power cable, data cable) is the box before you close it.<br /> <br /> Then you can go on downloading next receiver. You can re-start the software (Shortcut to DataXfer.exe), then it will detect the new receiver automatically.<br /> <br /> ===Downloading the Trimble Net-RS receiver===<br /> <br /> <br /> ===What goes on the data log sheet?===<br /> Data log sheets are used to record important information regarding the site/benchmark and the survey session. We record information about the site, such as the name, benchmark inscription, and location. It is important to log information about the equipment used; including serial numbers, and type of equipment. We record hieght information, direction, as well as time and duration of the survey. It is important to log who conducted the survey as well as any unusual things/mishaps that occured during the survey. Follow the link to a printable [http://www.gps.alaska.edu/tfour/Misc/Alaska_Log.pdf log sheet].<br /> <br /> ===Where do data log sheets go===<br /> In the filing cabinet, in a hanging file stored by GPS campaign.<br /> <br /> Every year, we send a copy of all log sheets to [http://www.unavco.org UNAVCO] for permanent archiving, along with the data files. Sometimes after a while it is easier to find the information from the [http://www.unavco.org/facility/data/data.html UNAVCO Data Archive] than it is to find our own log sheets in the filing cabinet.<br /> <br /> <br /> ===Converting files to RINEX===<br /> The final step in the fieldwork is to convert the data files to the RINEX format. RINEX stands for '''R'''eceiver '''IN'''dependent '''EX'''change format. It is an ASCII format that is publicly documented and agreed upon worldwide. In contrast, the Trimble .dat and .t00/.t01 files are proprietary formats that are only used by Trimble. Naturally, every receiver manufacturer has its own proprietary format. There is a more compact binary format called BINEX that is meant to store the same information. BINEX has been adopted as the standard format for [http://pbo.unavco.org PBO], and may one day become the standard instead of RINEX.<br /> <br /> There are enough steps in the process that [[RINEXing|a complete guide]] is on its own page.<br /> <br /> <br /> ===Field Notes===<br /> [[Field Notes]] on successful and not-so-successful field excursions may help you plan your next trip.</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Fieldwork&diff=600 Fieldwork 2008-07-28T19:59:32Z

<p>Yuning: </p> <hr /> <div>:''Reach site, hunt around,''<br /> :''Setup, precise centering,''<br /> :''Yellow box takes data.''<br /> ::''- A concise guide to GPS fieldwork''<br /> <br /> Perhaps the most important thing to remember about GPS fieldwork is that with a 24-hour GPS survey you can measure the position of the GPS antenna to within about 2 mm horizontal precision and 6 mm vertical precision, and you can measure the vector between two GPS antennas even more precisely than that. What this means is that the tolerances for setup error are very tight and you have to be very careful. If not, YOU are likely to be the limiting error source in the measurements. It also means that you really can't hide it if you screw up. So do your best if you make a mistake or something odd happens, carefully record it on the log sheet. It is far better to know we have a bad observation than to find out years later.<br /> <br /> ===Where can I find site information?===<br /> We maintain a [http://gps.alaska.edu/gps GPS Site Database] that in theory stores site information from all the GPS sites we use. In practice, some are missing, but the database is mostly complete for Alaska and environs. You can search the database by 4 characeter ID, or radial or rectangular searches, and other ways as well. To access the database, you need a login and password, and for that you need to ask Jeff.<br /> <br /> ===Traveling in Alaska===<br /> <br /> Before you go on official University travel be sure to fill out a Travel Authorization (TA) form. You can get this from Candice Lake on the 6th floor in the buisness office. Even if you do not expect to spend money on the trip, it is important that you fill out this form for insurance purposes. When you return it is necessary to fill out an expense report (to be sure you are reimbursed for incurred costs), even if you had no expenses.<br /> <br /> <b>Rental Cars</b><br><br /> A rental is often the cheapest way to travel on the road network in Alaska. If you are traveling on University buisness (fieldwork falls in this <br /> category) then the university covers the insurance, be sure to decline coverage when renting the car. Be sure to print [http://gps.alaska.edu/tfour/Misc/travel_papers.pdf this document] when traveling in a rental car; it contains [http://gps.alaska.edu/tfour/Misc/travel_papers.pdf proof of insurance] and some phone numbers to call if an accident occurs. The GI recommends that you '''not''' rent from Budget due to their aggressive collection agency should damages occur to the vehicle while in your possesion. The GI recommends using [http://www.avis.com Avis] or some other rental company. Do not rent from the airport rental location, there is an additional 10% tax plus fees added to the price of rental if you rent from the airport. Most of the rental companies have other locations in town, which have lower costs. <br /> <br /> <b>Flying in the Bush</b><br><br /> This is not your regular commercial flight, get all the information you need prior to departure.<br /> <br /> ===How to set up a tripod===<br /> <br /> There are as many different explanations as people who have set up a tripod before. Well, one description you can use is this: Follow the link to a printable [http://www.gps.alaska.edu/tfour/Misc/tripodsetup1.pdf setup description] and/or the link to [[new site and tripod setup description]].<br /> <br /> ===How to set up a spike mount===<br /> 1) Locate benchmark with hand-held GPS or site description.<br /> <br /> 2) Assemble spike mount by attaching legs to spike.<br /> a. *Out of the case the legs on the spike mount will be short. Use the leg extensions as needed to improve stability.<br /> b. Additional wing-nuts, lock washers and spike tips are included in the case<br /> 3) Set the spike on the benchmark with the legs oriented at 90 degrees from each other, or as close to 90 as possible.<br /> <br /> 4) Loosely tighten the wing-nut on the leg extensions to hold the leg lengths.<br /> <br /> 5) Use the carpenter’s level and the leg screws to level each leg independently.<br /> <br /> 6) Loosen the wing nuts and add weights (rocks) to hold the leg positions, retighten the wing nuts.<br /> <br /> 7) Attach the leveling plate to the spike and place the bull’s-eye level on the plate.<br /> <br /> 8) Use the leg screw to level the plate. Once the plate is level tighten the locking nut on the legs.<br /> <br /> 9) Remove the leveling plate.<br /> <br /> 10) Attach the antenna to the spike. ** Do not attach the antenna cable yet.**<br /> a. Make sure at least one spike clamp is tight, to ensure that the spike doesn’t rotate when tightening the antenna.<br /> 11) Orient the antenna to north.<br /> a. Set the declination on your compass, the compass can be placed directly onto the antenna. <br /> b. Some antennas are marked with a North arrow others are not. If there is no North direction indicated, Notch 1 <br /> (located at the edge on the antenna) should be pointed north.<br /> c. The antenna will likely need to be rotated. Loosen the spike clamps and rotate in the clockwise (tightening)<br /> direction.<br /> 12) Hook the receiver up to power.<br /> <br /> 13) Attach the antenna cable to receiver and antenna.<br /> <br /> ===Orienting the antenna to TRUE NORTH===<br /> Every antenna has a reference line or arrow that must be oriented toward TRUE NORTH. The reason for this is that the position actually measured by GPS is something called the ''antenna phase center'', which in general is not located on the axis of the antenna. So if you orient the antenna in some other direction, you introduce an error into the resulting postion that for many antennas is much larger than the measurement uncertainty.<br /> :The reference arrow for the Trimble 4000's antenna is marked on the antenna.<br /> :For other antennas, the antenna cable connector should point to NORTH. There will normally be something marked on the top of the antenna along that same line.<br /> <br /> To orient the antenna, you need to know the magnetic declination. It should be recorded on the site description. If not, it can be found on any USGS topo map. If all else fails, remember 25 degrees east, which is not too far off for most of central and southern Alaska.<br /> :If the declination is EAST, set your compass to 360 - declination and orient by the north arrow on the compass.<br /> :If the declination is WEST, set your compass to 360 + declination and orient by the north arrow on the compass.<br /> <br /> If you find that you oriented the antenna the wrong way, and it is already recording data, don't do anything rash! The best thing to do in this case is to carefully record the actual orientation of the antenna. <br /> <br /> ===Programming a Trimble 4000 receiver===<br /> You can find a printable description of a [http://www.gps.alaska.edu/tfour/Misc/ReceiverSetup_multiday.pdf multi-day receiver setup] by clicking on that link.<br /> <br /> ===Using the Trimble 5700 and R7 receivers===<br /> These two receivers are basically the same thing. Neither one is convenient to program in the field. Turn them on and they should work.<br /> <br /> What the lights mean.<br /> <br /> <br /> ===Using the Trimble Net-RS receiver===<br /> <br /> The main issue with the Net-RS receiver is that it writes all data for one UTC day into ONE file. This must be<br /> considered when a station is moved within one UTC day between sites. It is possible to untangle the data but still it's a hassle. In Alaska a new UTC day starts at 4:00 pm, meaning that taking the station down before 4 pm and setting it out somewhere else after 4 pm would be ideal.<br /> <br /> If you must visit 2 sites on the same Julian day, here is a way to get the data to go into separate files. You'll need a laptop, and a crossover (Xover) ethernet cable. Set your network settings on the laptop to IP: 192.168.1.3 NetMask: 255.255.255.0 Gateway: 192.168.1.1<br /> Connect the laptop to the NetRS. Open internet explorer or equiv. and go to the site 192.168.1.2<br /> The web interface should appear with a blue background. Under Data Logging, switch from one 30sec 24hour session to another by toggling the appropriate "enable" boxes. If you need to program a second campaign session, read the manual.<br /> <br /> ATTN: The Net-RS receiver has different power and antenna inputs! Make sure you have the right cables (usually they do not fit into the black case) before you leave the vehicle, especially when the site is away from the road.<br /> <br /> ===Using the Topcon GB-1000 receiver===<br /> There is printable introduction here: [http://gps.alaska.edu/~yuning/topcongb1000.pdf]<br /> <br /> ===Downloading the Trimble 4000 receiver===<br /> <br /> <br /> ===Downloading the Trimble 5700 receiver===<br /> <br /> We will use the "Windows system" computer to download data from Trimber 5700 receiver. And also make sure that log sheet is at your hand.<br /> <br /> 1. Take the Trimble 5700 receiver out from the yellow box (I know it's "crap", but it's exact what we do first).<br /> <br /> 2. There are two cables needed to plug into the receiver: power cable (circle); data cable (a little bit rectangular). Power on the receiver.<br /> <br /> 3. Double click "Shortcut to DataXfer.exe" on the computer desktop. If the receiver is already connected, the software will display the receiver and its series number, check the number and what was recorded on the log sheet, make sure they are matched.<br /> <br /> 4. Click the "add" button, then you can see all the recorded data in the receiver. Choose the data you want to download, and make sure save the data file to directory E:\GPSdata\. For example, if we want to download compaign data of KENAI trip in 2008, the subdirectory can be created as E:\GPSdata\data 2008\campaign\kenai, and the downloaded data should go to there. Then, click "Transfer", then you will see the computer doing its work to download data. And you need to click "OK" during the download.<br /> <br /> 5. Change files name. Usually, there are two files for one day of one site: *.dat and *.T00. Change the first 4 letters to site name for both of these two files. For example, for site DAHL, the data file name should be changed to the format like this: "dahl1430.dat" and "dahl1430.T00" (143 is the Julian day). If the name of site has only 3 letters (site CPR, for example), then names should be like this: "cpr_1450.dat" and "cpr_1450.T01". <br /> <br /> 6. The download work is done. Power off receiver and put the receiver back to the yellow box. Check if all the stuff (receiver, antenna, power cable, data cable) is the box before you close it.<br /> <br /> Then you can go on downloading next receiver. You can re-start the software (Shortcut to DataXfer.exe), then it will detect the new receiver automatically.<br /> <br /> ===Downloading the Trimble Net-RS receiver===<br /> <br /> <br /> ===What goes on the data log sheet?===<br /> Data log sheets are used to record important information regarding the site/benchmark and the survey session. We record information about the site, such as the name, benchmark inscription, and location. It is important to log information about the equipment used; including serial numbers, and type of equipment. We record hieght information, direction, as well as time and duration of the survey. It is important to log who conducted the survey as well as any unusual things/mishaps that occured during the survey. Follow the link to a printable [http://www.gps.alaska.edu/tfour/Misc/Alaska_Log.pdf log sheet].<br /> <br /> ===Where do data log sheets go===<br /> In the filing cabinet, in a hanging file stored by GPS campaign.<br /> <br /> Every year, we send a copy of all log sheets to [http://www.unavco.org UNAVCO] for permanent archiving, along with the data files. Sometimes after a while it is easier to find the information from the [http://www.unavco.org/facility/data/data.html UNAVCO Data Archive] than it is to find our own log sheets in the filing cabinet.<br /> <br /> <br /> ===Converting files to RINEX===<br /> The final step in the fieldwork is to convert the data files to the RINEX format. RINEX stands for '''R'''eceiver '''IN'''dependent '''EX'''change format. It is an ASCII format that is publicly documented and agreed upon worldwide. In contrast, the Trimble .dat and .t00/.t01 files are proprietary formats that are only used by Trimble. Naturally, every receiver manufacturer has its own proprietary format. There is a more compact binary format called BINEX that is meant to store the same information. BINEX has been adopted as the standard format for [http://pbo.unavco.org PBO], and may one day become the standard instead of RINEX.<br /> <br /> There are enough steps in the process that [[RINEXing|a complete guide]] is on its own page.<br /> <br /> <br /> ===Field Notes===<br /> [[Field Notes]] on successful and not-so-successful field excursions may help you plan your next trip.</div>

Yuning http://gps.alaska.edu/internal/index.php?title=Fieldwork&diff=599 Fieldwork 2008-07-28T19:49:53Z

<p>Yuning: </p> <hr /> <div>:''Reach site, hunt around,''<br /> :''Setup, precise centering,''<br /> :''Yellow box takes data.''<br /> ::''- A concise guide to GPS fieldwork''<br /> <br /> Perhaps the most important thing to remember about GPS fieldwork is that with a 24-hour GPS survey you can measure the position of the GPS antenna to within about 2 mm horizontal precision and 6 mm vertical precision, and you can measure the vector between two GPS antennas even more precisely than that. What this means is that the tolerances for setup error are very tight and you have to be very careful. If not, YOU are likely to be the limiting error source in the measurements. It also means that you really can't hide it if you screw up. So do your best if you make a mistake or something odd happens, carefully record it on the log sheet. It is far better to know we have a bad observation than to find out years later.<br /> <br /> ===Where can I find site information?===<br /> We maintain a [http://gps.alaska.edu/gps GPS Site Database] that in theory stores site information from all the GPS sites we use. In practice, some are missing, but the database is mostly complete for Alaska and environs. You can search the database by 4 characeter ID, or radial or rectangular searches, and other ways as well. To access the database, you need a login and password, and for that you need to ask Jeff.<br /> <br /> ===Traveling in Alaska===<br /> <br /> Before you go on official University travel be sure to fill out a Travel Authorization (TA) form. You can get this from Candice Lake on the 6th floor in the buisness office. Even if you do not expect to spend money on the trip, it is important that you fill out this form for insurance purposes. When you return it is necessary to fill out an expense report (to be sure you are reimbursed for incurred costs), even if you had no expenses.<br /> <br /> <b>Rental Cars</b><br><br /> A rental is often the cheapest way to travel on the road network in Alaska. If you are traveling on University buisness (fieldwork falls in this <br /> category) then the university covers the insurance, be sure to decline coverage when renting the car. Be sure to print [http://gps.alaska.edu/tfour/Misc/travel_papers.pdf this document] when traveling in a rental car; it contains [http://gps.alaska.edu/tfour/Misc/travel_papers.pdf proof of insurance] and some phone numbers to call if an accident occurs. The GI recommends that you '''not''' rent from Budget due to their aggressive collection agency should damages occur to the vehicle while in your possesion. The GI recommends using [http://www.avis.com Avis] or some other rental company. Do not rent from the airport rental location, there is an additional 10% tax plus fees added to the price of rental if you rent from the airport. Most of the rental companies have other locations in town, which have lower costs. <br /> <br /> <b>Flying in the Bush</b><br><br /> This is not your regular commercial flight, get all the information you need prior to departure.<br /> <br /> ===How to set up a tripod===<br /> <br /> There are as many different explanations as people who have set up a tripod before. Well, one description you can use is this: Follow the link to a printable [http://www.gps.alaska.edu/tfour/Misc/tripodsetup1.pdf setup description] and/or the link to [[new site and tripod setup description]].<br /> <br /> ===How to set up a spike mount===<br /> 1) Locate benchmark with hand-held GPS or site description.<br /> <br /> 2) Assemble spike mount by attaching legs to spike.<br /> a. *Out of the case the legs on the spike mount will be short. Use the leg extensions as needed to improve stability.<br /> b. Additional wing-nuts, lock washers and spike tips are included in the case<br /> 3) Set the spike on the benchmark with the legs oriented at 90 degrees from each other, or as close to 90 as possible.<br /> <br /> 4) Loosely tighten the wing-nut on the leg extensions to hold the leg lengths.<br /> <br /> 5) Use the carpenter’s level and the leg screws to level each leg independently.<br /> <br /> 6) Loosen the wing nuts and add weights (rocks) to hold the leg positions, retighten the wing nuts.<br /> <br /> 7) Attach the leveling plate to the spike and place the bull’s-eye level on the plate.<br /> <br /> 8) Use the leg screw to level the plate. Once the plate is level tighten the locking nut on the legs.<br /> <br /> 9) Remove the leveling plate.<br /> <br /> 10) Attach the antenna to the spike. ** Do not attach the antenna cable yet.**<br /> a. Make sure at least one spike clamp is tight, to ensure that the spike doesn’t rotate when tightening the antenna.<br /> 11) Orient the antenna to north.<br /> a. Set the declination on your compass, the compass can be placed directly onto the antenna. <br /> b. Some antennas are marked with a North arrow others are not. If there is no North direction indicated, Notch 1 <br /> (located at the edge on the antenna) should be pointed north.<br /> c. The antenna will likely need to be rotated. Loosen the spike clamps and rotate in the clockwise (tightening)<br /> direction.<br /> 12) Hook the receiver up to power.<br /> <br /> 13) Attach the antenna cable to receiver and antenna.<br /> <br /> ===Orienting the antenna to TRUE NORTH===<br /> Every antenna has a reference line or arrow that must be oriented toward TRUE NORTH. The reason for this is that the position actually measured by GPS is something called the ''antenna phase center'', which in general is not located on the axis of the antenna. So if you orient the antenna in some other direction, you introduce an error into the resulting postion that for many antennas is much larger than the measurement uncertainty.<br /> :The reference arrow for the Trimble 4000's antenna is marked on the antenna.<br /> :For other antennas, the antenna cable connector should point to NORTH. There will normally be something marked on the top of the antenna along that same line.<br /> <br /> To orient the antenna, you need to know the magnetic declination. It should be recorded on the site description. If not, it can be found on any USGS topo map. If all else fails, remember 25 degrees east, which is not too far off for most of central and southern Alaska.<br /> :If the declination is EAST, set your compass to 360 - declination and orient by the north arrow on the compass.<br /> :If the declination is WEST, set your compass to 360 + declination and orient by the north arrow on the compass.<br /> <br /> If you find that you oriented the antenna the wrong way, and it is already recording data, don't do anything rash! The best thing to do in this case is to carefully record the actual orientation of the antenna. <br /> <br /> ===Programming a Trimble 4000 receiver===<br /> You can find a printable description of a [http://www.gps.alaska.edu/tfour/Misc/ReceiverSetup_multiday.pdf multi-day receiver setup] by clicking on that link.<br /> <br /> ===Using the Trimble 5700 and R7 receivers===<br /> These two receivers are basically the same thing. Neither one is convenient to program in the field. Turn them on and they should work.<br /> <br /> What the lights mean.<br /> <br /> <br /> ===Using the Trimble Net-RS receiver===<br /> <br /> The main issue with the Net-RS receiver is that it writes all data for one UTC day into ONE file. This must be<br /> considered when a station is moved within one UTC day between sites. It is possible to untangle the data but still it's a hassle. In Alaska a new UTC day starts at 4:00 pm, meaning that taking the station down before 4 pm and setting it out somewhere else after 4 pm would be ideal.<br /> <br /> If you must visit 2 sites on the same Julian day, here is a way to get the data to go into separate files. You'll need a laptop, and a crossover (Xover) ethernet cable. Set your network settings on the laptop to IP: 192.168.1.3 NetMask: 255.255.255.0 Gateway: 192.168.1.1<br /> Connect the laptop to the NetRS. Open internet explorer or equiv. and go to the site 192.168.1.2<br /> The web interface should appear with a blue background. Under Data Logging, switch from one 30sec 24hour session to another by toggling the appropriate "enable" boxes. If you need to program a second campaign session, read the manual.<br /> <br /> ATTN: The Net-RS receiver has different power and antenna inputs! Make sure you have the right cables (usually they do not fit into the black case) before you leave the vehicle, especially when the site is away from the road.<br /> <br /> ===Using the Topcon GB-1000 receiver===<br /> <br /> <br /> ===Downloading the Trimble 4000 receiver===<br /> <br /> <br /> ===Downloading the Trimble 5700 receiver===<br /> <br /> We will use the "Windows system" computer to download data from Trimber 5700 receiver. And also make sure that log sheet is at your hand.<br /> <br /> 1. Take the Trimble 5700 receiver out from the yellow box (I know it's "crap", but it's exact what we do first).<br /> <br /> 2. There are two cables needed to plug into the receiver: power cable (circle); data cable (a little bit rectangular). Power on the receiver.<br /> <br /> 3. Double click "Shortcut to DataXfer.exe" on the computer desktop. If the receiver is already connected, the software will display the receiver and its series number, check the number and what was recorded on the log sheet, make sure they are matched.<br /> <br /> 4. Click the "add" button, then you can see all the recorded data in the receiver. Choose the data you want to download, and make sure save the data file to directory E:\GPSdata\. For example, if we want to download compaign data of KENAI trip in 2008, the subdirectory can be created as E:\GPSdata\data 2008\campaign\kenai, and the downloaded data should go to there. Then, click "Transfer", then you will see the computer doing its work to download data. And you need to click "OK" during the download.<br /> <br /> 5. Change files name. Usually, there are two files for one day of one site: *.dat and *.T00. Change the first 4 letters to site name for both of these two files. For example, for site DAHL, the data file name should be changed to the format like this: "dahl1430.dat" and "dahl1430.T00" (143 is the Julian day). If the name of site has only 3 letters (site CPR, for example), then names should be like this: "cpr_1450.dat" and "cpr_1450.T01". <br /> <br /> 6. The download work is done. Power off receiver and put the receiver back to the yellow box. Check if all the stuff (receiver, antenna, power cable, data cable) is the box before you close it.<br /> <br /> Then you can go on downloading next receiver. You can re-start the software (Shortcut to DataXfer.exe), then it will detect the new receiver automatically.<br /> <br /> ===Downloading the Trimble Net-RS receiver===<br /> <br /> <br /> ===What goes on the data log sheet?===<br /> Data log sheets are used to record important information regarding the site/benchmark and the survey session. We record information about the site, such as the name, benchmark inscription, and location. It is important to log information about the equipment used; including serial numbers, and type of equipment. We record hieght information, direction, as well as time and duration of the survey. It is important to log who conducted the survey as well as any unusual things/mishaps that occured during the survey. Follow the link to a printable [http://www.gps.alaska.edu/tfour/Misc/Alaska_Log.pdf log sheet].<br /> <br /> ===Where do data log sheets go===<br /> In the filing cabinet, in a hanging file stored by GPS campaign.<br /> <br /> Every year, we send a copy of all log sheets to [http://www.unavco.org UNAVCO] for permanent archiving, along with the data files. Sometimes after a while it is easier to find the information from the [http://www.unavco.org/facility/data/data.html UNAVCO Data Archive] than it is to find our own log sheets in the filing cabinet.<br /> <br /> <br /> ===Converting files to RINEX===<br /> The final step in the fieldwork is to convert the data files to the RINEX format. RINEX stands for '''R'''eceiver '''IN'''dependent '''EX'''change format. It is an ASCII format that is publicly documented and agreed upon worldwide. In contrast, the Trimble .dat and .t00/.t01 files are proprietary formats that are only used by Trimble. Naturally, every receiver manufacturer has its own proprietary format. There is a more compact binary format called BINEX that is meant to store the same information. BINEX has been adopted as the standard format for [http://pbo.unavco.org PBO], and may one day become the standard instead of RINEX.<br /> <br /> There are enough steps in the process that [[RINEXing|a complete guide]] is on its own page.<br /> <br /> <br /> ===Field Notes===<br /> [[Field Notes]] on successful and not-so-successful field excursions may help you plan your next trip.</div>

Yuning http://gps.alaska.edu/internal/index.php?title=RoiPac&diff=1598 RoiPac 2008-07-23T00:34:43Z

<p>Yuning: /* Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC. */</p> <hr /> <div>Our lab has installed ROI_PAC 3.0 for SAR and InSAR processing. Some detailed introductions and explainations will be followed soon. And also, you can get information about InSAR and ROI_PAC from the links below.<br /> <br /> http://roipac.org/<br /> <br /> http://www.uoregon.edu/~das/WikiRoiPac/doku.php?id=welcome<br /> <br /> === ROI_PAC ===<br /> <br /> ROI_PAC is located at /usr/local/ROI_PAC_3_0, and there is also SAR data available for your test at /usr/local/TEST_DIR directory. More information about how to play with it will be updated soon.<br /> <br /> ===Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC.===<br /> <br /> Take the test data (/usr/local/TEST_DIR) for example to explain the processing.<br /> <br /> First, compile some environment variable and path used by ROI_PCA. There is already a template file named SAR_CONFIG at /usr/local/ROI_PAC_3_0/ROI_PAC. Change the necessary commands, and then "source" it.<br /> <br /> source SAR_CONFIG<br /> <br /> <br /> Then, ingest the data. Go to the SAR data directory (/usr/local/TEST_DIR/930110 and /usr/local/TEST_DIR/950523), and ingest data respectively. <br /> <br /> TEST_DIR/930110> make_raw.pl PRC SARLEADER1993011018252739T1Of1 930110 <br /> TEST_DIR/950523> make_raw.pl PRC SARLEADER1995052318253409T1Of1 950523 <br /> <br /> Note: Different SAR data format has different command to ingest. For our case, they are ERS data, so "make_raw.pl" is used.<br /> <br /> Last, data processing. Actually, there is a command "process_2pass.pl" can run all the steps after raw data ready. And the file "int.proc" in main directory (/usr/local/TEST_DIR) specifiles two scene directories (data and orbit) and other processing parameters for a given interferogram.<br /> <br /> process_2pass.pl int.proc<br /> <br /> And also, we can do it step by step.<br /> <br /> process_2pass.pl int.proc [DoItFrom EndItAt]<br /> <br /> DoItFrom = point in process.pl to start<br /> EndItAt = point in process.pl to end<br /> Can be: raw, roi_prep, orbbase, slcs, offsets, resamp, flatorb, full_res, filtered, make_mask, unwrapped, simulation, morph_sim, <br /> redo_base or use_sim_base<br /> EndItAt can also be synth_offset<br /> <br /> For more information about ROI_PAC, please refer POI_PAC [http://roipac.org/ website] and Eric Fielding's ppt [http://gps.alaska.edu/~yuning/Eric_Roipac.ppt "ROI-pac Internals"].<br /> <br /> And also, you can look at Andrew Newman's introduction for ROI_PAC processing here:<br /> http://geophysics.eas.gatech.edu/people/anewman/classes/MGM/InSAR/Setup.html</div>

Yuning http://gps.alaska.edu/internal/index.php?title=RoiPac&diff=597 RoiPac 2008-07-21T23:22:58Z

<p>Yuning: /* Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC. */</p> <hr /> <div>Our lab has installed ROI_PAC 3.0 for SAR and InSAR processing. Some detailed introductions and explainations will be followed soon. And also, you can get information about InSAR and ROI_PAC from the links below.<br /> <br /> http://roipac.org/<br /> <br /> http://www.uoregon.edu/~das/WikiRoiPac/doku.php?id=welcome<br /> <br /> === ROI_PAC ===<br /> <br /> ROI_PAC is located at /usr/local/ROI_PAC_3_0, and there is also SAR data available for your test at /usr/local/TEST_DIR directory. More information about how to play with it will be updated soon.<br /> <br /> ===Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC.===<br /> <br /> Take the test data (/usr/local/TEST_DIR) for example to explain the processing.<br /> <br /> First, compile some environment variable and path used by ROI_PCA. There is already a template file named SAR_CONFIG at /usr/local/ROI_PAC_3_0/ROI_PAC. Change the necessary commands, and then "source" it.<br /> <br /> source SAR_CONFIG<br /> <br /> <br /> Then, ingest the data. Go to the SAR data directory (/usr/local/TEST_DIR/930110 and /usr/local/TEST_DIR/950523), and ingest data respectively. <br /> <br /> TEST_DIR/930110> make_raw.pl PRC SARLEADER1993011018252739T1Of1 930110 <br /> TEST_DIR/950523> make_raw.pl PRC SARLEADER1995052318253409T1Of1 950523 <br /> <br /> Note: Different SAR data format has different command to ingest. For our case, they are ERS data, so "make_raw.pl" is used.<br /> <br /> Last, data processing. Actually, there is a command "process_2pass.pl" can run all the steps after raw data ready. And the file "int.proc" in main directory (/usr/local/TEST_DIR) specifiles two scene directories (data and orbit) and other processing parameters for a given interferogram.<br /> <br /> process_2pass.pl int.proc<br /> <br /> And also, we can do it step by step.<br /> <br /> process_2pass.pl int.proc [DoItFrom EndItAt]<br /> <br /> DoItFrom = point in process.pl to start<br /> EndItAt = point in process.pl to end<br /> Can be: raw, roi_prep, orbbase, slcs, offsets, resamp, flatorb, full_res, filtered, make_mask, unwrapped, simulation, morph_sim, <br /> redo_base or use_sim_base<br /> EndItAt can also be synth_offset<br /> <br /> For more information about ROI_PAC, please refer POI_PAC [http://roipac.org/ website] and Eric Fielding's ppt [http://gps.alaska.edu/~yuning/Eric_Roipac.ppt "ROI-pac Internals"].<br /> <br /> And also, you can look at Andrew Newman's introduction here:<br /> http://geophysics.eas.gatech.edu/people/anewman/classes/MGM/InSAR/Setup.html</div>

Yuning http://gps.alaska.edu/internal/index.php?title=RoiPac&diff=596 RoiPac 2008-07-21T18:15:16Z

<p>Yuning: /* Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC. */</p> <hr /> <div>Our lab has installed ROI_PAC 3.0 for SAR and InSAR processing. Some detailed introductions and explainations will be followed soon. And also, you can get information about InSAR and ROI_PAC from the links below.<br /> <br /> http://roipac.org/<br /> <br /> http://www.uoregon.edu/~das/WikiRoiPac/doku.php?id=welcome<br /> <br /> === ROI_PAC ===<br /> <br /> ROI_PAC is located at /usr/local/ROI_PAC_3_0, and there is also SAR data available for your test at /usr/local/TEST_DIR directory. More information about how to play with it will be updated soon.<br /> <br /> ===Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC.===<br /> <br /> Take the test data (/usr/local/TEST_DIR) for example to explain the processing.<br /> <br /> First, compile some environment variable and path used by ROI_PCA. There is already a template file named SAR_CONFIG at /usr/local/ROI_PAC_3_0/ROI_PAC. Change the necessary commands, and then "source" it.<br /> <br /> source SAR_CONFIG<br /> <br /> <br /> Then, ingest the data. Go to the SAR data directory (/usr/local/TEST_DIR/930110 and /usr/local/TEST_DIR/950523), and ingest data respectively. <br /> <br /> TEST_DIR/930110> make_raw.pl PRC SARLEADER1993011018252739T1Of1 930110 <br /> TEST_DIR/950523> make_raw.pl PRC SARLEADER1995052318253409T1Of1 950523 <br /> <br /> Note: Different SAR data format has different command to ingest. For our case, they are ERS data, so "make_raw.pl" is used.<br /> <br /> Last, data processing. Actually, there is a command "process_2pass.pl" can run all the steps after raw data ready. And the file "int.proc" in main directory (/usr/local/TEST_DIR) specifiles two scene directories (data and orbit) and other processing parameters for a given interferogram.<br /> <br /> process_2pass.pl int.proc<br /> <br /> And also, we can do it step by step.<br /> <br /> process_2pass.pl int.proc [DoItFrom EndItAt]<br /> <br /> DoItFrom = point in process.pl to start<br /> EndItAt = point in process.pl to end<br /> Can be: raw, roi_prep, orbbase, slcs, offsets, resamp, flatorb, full_res, filtered, make_mask, unwrapped, simulation, morph_sim, <br /> redo_base or use_sim_base<br /> EndItAt can also be synth_offset<br /> <br /> For more information about ROI_PAC, please refer POI_PAC [http://roipac.org/ website] and Eric Fielding's ppt [http://gps.alaska.edu/~yuning/Eric_Roipac.ppt "ROI-pac Internals"].</div>

Yuning http://gps.alaska.edu/internal/index.php?title=RoiPac&diff=595 RoiPac 2008-07-21T18:13:13Z

<p>Yuning: /* Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC. */</p> <hr /> <div>Our lab has installed ROI_PAC 3.0 for SAR and InSAR processing. Some detailed introductions and explainations will be followed soon. And also, you can get information about InSAR and ROI_PAC from the links below.<br /> <br /> http://roipac.org/<br /> <br /> http://www.uoregon.edu/~das/WikiRoiPac/doku.php?id=welcome<br /> <br /> === ROI_PAC ===<br /> <br /> ROI_PAC is located at /usr/local/ROI_PAC_3_0, and there is also SAR data available for your test at /usr/local/TEST_DIR directory. More information about how to play with it will be updated soon.<br /> <br /> ===Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC.===<br /> <br /> Take the test data (/usr/local/TEST_DIR) for example to explain the processing.<br /> <br /> First, compile some environment variable and path used by ROI_PCA. There is already a template file named SAR_CONFIG at /usr/local/ROI_PAC_3_0/ROI_PAC. Change the necessary commands, and then "source" it.<br /> <br /> source SAR_CONFIG<br /> <br /> <br /> Then, ingest the data. Go to the SAR data directory (/usr/local/TEST_DIR/930110 and /usr/local/TEST_DIR/950523), and ingest data respectively. <br /> <br /> TEST_DIR/930110> make_raw.pl PRC SARLEADER1993011018252739T1Of1 930110 <br /> TEST_DIR/950523> make_raw.pl PRC SARLEADER1995052318253409T1Of1 950523 <br /> <br /> Note: Different SAR data format has different commands to ingest. For our case, they are ERS data, so "make_raw.pl" is used.<br /> <br /> Last, data processing. Actually, there is a command "process_2pass.pl" can run all the steps after raw data ready. And the file "int.proc" in main directory (/usr/local/TEST_DIR) specifiles two scene directories (data and orbit) and other processing parameters for a given interferogram.<br /> <br /> process_2pass.pl int.proc<br /> <br /> And also, we can do it step by step.<br /> <br /> process_2pass.pl int.proc [DoItFrom EndItAt]<br /> <br /> DoItFrom = point in process.pl to start<br /> EndItAt = point in process.pl to end<br /> Can be: raw, roi_prep, orbbase, slcs, offsets, resamp, flatorb, full_res, filtered, make_mask, unwrapped, simulation, morph_sim, <br /> redo_base or use_sim_base<br /> EndItAt can also be synth_offset<br /> <br /> For more information about ROI_PAC, please refer POI_PAC [http://roipac.org/ website] and Eric Fielding's ppt [http://gps.alaska.edu/~yuning/Eric_Roipac.ppt "ROI-pac Internals"].</div>

Yuning http://gps.alaska.edu/internal/index.php?title=WHOS&diff=601 WHOS 2008-07-09T01:23:09Z

<p>Yuning: /* Week Schedule as of 9/7/07 */</p> <hr /> <div>The WHOS list tracks assigned GPS weeks for processing.<br /> <br /> More details about analysis at [[GPS analysis system]].<br /> <br /> ===Recent weeks===<br /> <pre><br /> week # start date last processed who status<br /> ****************************************************************<br /> 1375 05/14/2006 Trivikram/trivikram 1/ CLEAN EXCEPT 2 DAYS<br /> 1376 05/21/2006 Trivikram/1-2/ CLEAN<br /> 1377 05/28/2006 07/20/2006 Trivikram 1<br /> 1378 06/04/2006 07/20/2006 Trivikram 1 <br /> 1379 06/11/2006 07/20/2006 Trivikram 1 <br /> 1380 06/18/2006 07/20/2006 Trivikram 1 <br /> 1381 06/25/2006 07/12/2006 Ryan<br /> 1382 07/02/2006 Julie<br /> 1383 07/09/2006 Julie<br /> 1384 07/16/2006 Julie<br /> 1385 07/23/2006 Julie<br /> <br /> 1413 02/04/2007 05/01/2007 Tom<br /> </pre><br /> ===Week Schedule as of 9/7/07===<br /> <pre><br /> week # start date last processed who status<br /> *************************************************************<br /> 1430 Brandon NEAsia Alaska and NOAM-clean<br /> <br /> 1431 09/??/2007 10/31/2007 Lissy AK - clean<br /> 1431 11/05/2007 01/??/2008 Lissy initial cleaning done for Tibet solution<br /> 1431 01/09/2008 Lissy Casa solutions started<br /> <br /> 1432 Yuning initial cleaning done<br /> 1433 09/14/2007 09/26/2007 Ronni 1st iteration <br /> 1434 Julie<br /> 1435 Julie<br /> 1436 Julie<br /> 1437 Julie<br /> 1438 Julie<br /> 1439 Brandon one more iteration<br /> 1440 12?/??/2007 Lissy<br /> 1441 Yuning initial cleaning done<br /> 1442 09/27/2007 Ronni initial cleaning done<br /> 1443 Brandon NEA clean<br /> 1444 01/16/2008 Lissy<br /> 1445 Yuning initial cleaning done<br /> 1446 03/11/2008 Ronni<br /> 1447 Brandon initial cleaning done<br /> 1448 11/16/2007 05/12/2008 Lissy initial cleaning done<br /> 1449 Brandon NEA and Alaska cleaned<br /> 1450 Brandon initial cleaning done<br /> 1451 Brandon initial cleaning done<br /> 1452 01/23/2008 01/28/2008 Lissy initial cleaning done for Tibet & casa solution <br /> 1453 Yuning initial cleaning done<br /> 1454 05/05/2008 Ronni AK first interation<br /> 1455 Brandon initial cleaning done<br /> 1456 01/28/2008 Lissy<br /> 1457 Yuning initial cleaning done<br /> 1458 05/05/2008 Ronni AK first interation<br /> 1459 Julie<br /> 1460 Brandon NEA and AK cleaned<br /> 1461 02/06/2008 Lissy<br /> 1462 Yuning initial cleaning done<br /> 1463 05/05/2008 Ronni AK first interation<br /> 1464 Julie<br /> 1465 Brandon initial cleaning done<br /> 1466 04/09/2008 Lissy<br /> 1467 Yuning AK cleaning done<br /> 1468 05/05/2008 Ronni AK first interation<br /> 1469 Julie<br /> 1470 Brandon initial cleaning done<br /> 1471 04/09/2008 Lissy<br /> 1472 Yuning AK cleaning done<br /> 1473 05/05/2008 Ronni AK first interation<br /> 1474 Julie<br /> 1475 Brandon<br /> 1476 Lissy<br /> 1477 Yuning AK cleaning done<br /> 1478 05/05/2008 Ronni AK first interation<br /> 1479 Julie<br /> 1480 Brandon<br /> 1481 Lissy<br /> 1482 Yuning<br /> 1483 Ronni<br /> 1484 Julie<br /> 1485 Brandon<br /> 1486 Lissy<br /> 1487 Yuning<br /> 1488 Ronni<br /> 1489 Julie<br /> 1490 Brandon<br /> 1491 Lissy<br /> 1492 Yuning<br /> 1493 Ronni<br /> 1494 Julie<br /> 1495 Brandon<br /> 1496 Lissy<br /> 1497 Yuning<br /> 1498 Ronni<br /> 1499 Julie<br /> 1500 Brandon<br /> <br /> </pre><br /> <br /> ===2006===<br /> <pre><br /> week # start date last processed who status<br /> ****************************************************************<br /> 1357 01/08/2006 Sandeep CLEANING Venkat<br /> 1358 01/15/2006 Sandeep CLEANING Venkat<br /> 1359 01/22/2006 Sandeep CLEAN Venkat (AK Point File Size < 300)<br /> 1360 01/29/2006 Sandeep CLEANING Venkat<br /> 1361 02/05/2006 Trivikram<br /> 1362 02/12/2006 Trivikram CLEAN (AK Point file size < 400)<br /> 1363 02/19/2006 Venkat CLEAN (AK Point file size < 400)<br /> 1364 02/26/2006 Trivikram<br /> 1365 03/05/2006 Venkat CLEANING <br /> 1366 03/12/2006 Trivikram<br /> 1367 03/19/2006 Trivikram <br /> 1368 03/26/2006 Trivikram problem with AK CLEANING SOLN<br /> 1369 04/02/2006 Trivikram CLEAN<br /> 1370 04/09/2006 Tom <br /> 1371 04/16/2006 Venkat CLEANING<br /> 1372 04/23/2006 Venkat CLEANING <br /> 1373 04/30/2006 Venkat CLEANING<br /> 1374 05/07/2006 Venkat CLEANING<br /> </pre><br /> <br /> ===2005===<br /> <pre><br /> week # start date last processed who status<br /> ****************************************************************<br /> 1304 01/02/2005 09/16/2005 Ryan CLEAN<br /> 1305 01/09/2005 08/30/2005 Pravee CLEAN<br /> 1306 01/16/2005 07/15/2005 Jill WORKING Trivikram(tibet) 07/26/2006 CLEAN<br /> 1307 01/23/2005 08/31/2005 Pravee CLEAN Trivikram(tibet) 07/26/2006 CLEAN<br /> 1308 01/30/2005 04/05/2005 Jill CLEAN Trivikram(tibet) 07/26/2006 CLEAN<br /> 1309 02/06/2005 08/31/2005 Pravee CLEAN <br /> 1310 02/13/2005 03/12/2005 Julie CLEAN <br /> 1311 02/20/2005 03/12/2005 Pravee CLEANING<br /> 1312 02/27/2005 03/31/2005 Tom CLEAN<br /> 1313 03/06/2005 03/31/2005 Pravee CLEANING<br /> 1314 03/13/2005 03/31/2005 Tom CLEAN<br /> 1315 03/20/2005 06/13/2005 Samik CLEAN (Point File Size < 500)<br /> 1316 03/27/2005 06/13/2005 Samik CLEAN (Point File Size < 400) <br /> 1317 04/03/2005 06/16/2005 Samik CLEAN (Point File Size < 400)<br /> 1318 04/10/2005 9/15/2005 Ryan not sure what's going on?<br /> 1319 04/17/2005 10/4/2005 Ryan ak SUBMITTED<br /> 1320 04/24/2005 Sandeep Done 1 2 Trivikram(tibet) 07/27/2006 1 2 CLEAN except 2 days<br /> 1321 05/01/2005 Sandeep Done 1 2 Trivikram(tibet) 07/28/2006 1 <br /> 1322 05/08/2005 Sandeep Done 1 2 Trivikram(tibet) 07/28/2006 1<br /> 1323 05/15/2005 Sandeep Done 1 2 Trivikram(tibet) 08/04/2006 1 <br /> 1324 05/22/2005 Sandeep Done 1 2 Trivikram(tibet) 08/04/2006 1<br /> 1325 05/29/2005 Sigrun DONE Trivikram(tibet) 08/04/2006 1<br /> 1326 06/05/2005 Sigrun DONE Trivikram(tibet) 08/06/2006 1<br /> 1327 06/12/2005 Sandeep Done 1 2 NO TIBET<br /> 1328 06/19/2005 Sandeep Done 1 2 No TIBET<br /> 1329 06/26/2005 Sandeep Done 1 2 Trivikram(tibet) 08/18/2006 1<br /> 1330 07/03/2005 9/14/2005 Ryan DONE<br /> 1331 07/10/2005 11/10/2005 Tom Submitted<br /> 1332 07/17/2005 Sandeep CLEAN Venkat (AK Point File Size < 500)<br /> 1333 07/24/2005 Sandeep CLEAN Trivikram <br /> 1334 07/31/2005 Sandeep CLEAN Trivikram <br /> 1335 08/07/2005 9/12/2005 Tom CLEAN Venkat (AK Point File Size < 400)<br /> 1336 08/14/2005 Sandeep CLEAN Venkat (AK Point File Size < 300)<br /> 1337 08/21/2005 10/17/2005 Ryan ak CLEAN Venkat (AK Point File Size < 300) <br /> 1338 08/28/2005 10/17/2005 Ryan ak CLEAN Venkat (AK Point File Size < 300) <br /> 1339 09/04/2005 11/08/2005 Ryan CLEAN Trivikram (AK Point File Size < 300) <br /> 1340 09/11/2005 Sandeep CLEAN Venkat (AK Point File Size < 300)<br /> 1341 09/18/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1342 09/25/2005 Sandeep CLEAN Venkat (AK Point File Size < 300) <br /> 1343 10/02/2005 Sandeep CLEAN Venkat (AK Point File Size < 300)<br /> 1344 10/09/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1345 10/16/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1346 10/23/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1347 10/30/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1348 11/06/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1349 11/13/2005 Sandeep CLEAN Venkat (AK Point File Size < 300) <br /> 1350 11/20/2005 Sandeep CLEAN Venkat (AK Point File Size < 400) <br /> 1351 11/27/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1352 12/04/2005 Sandeep CLEAN Venkat (AK Point File Size < 300) <br /> 1353 12/11/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1354 12/18/2005 Sandeep CLEANING Venkat<br /> 1356 12/25/2005 Sandeep CLEANING Venkat<br /> </pre><br /> <br /> ===Older Stuff===<br /> <pre><br /> week # start date last processed who status<br /> ****************************************************************<br /> ****************************************************************<br /> ***************************2002*********************************<br /> **************************EARTHQUAKE****************************<br /> 1189 10/20/02 02/26/05 Josh PENDING<br /> 1190 10/27/02 Josh PENDING<br /> 1191 11/03/02 03/04/05 Josh DONE<br /> 1192 11/10/02 03/11/05 Josh DONE<br /> 1193 11/17/02 03/11/05 Josh DONE<br /> 1194 11/24/02 03/11/05 Josh DONE<br /> 1195 12/01/02 03/11/05 Josh RUNNING<br /> 1196 12/08/02 03/11/05 Josh DONE<br /> 1197 12/15/02 03/11/05 Josh DONE<br /> 1198 12/22/02 03/12/05 Josh DONE<br /> 1199 12/29/02 03/12/05 Josh DONE<br /> <br /> *************************2003***********************************<br /> <br /> 1200 01/05/03 03/12/05 Josh DONE<br /> 1201 01/12/03 03/12/05 Josh DONE<br /> 1202 01/19/03 03/15/05 Josh RUNNING<br /> 1203 01/26/03 03/14/05 Josh DONE<br /> 1204 02/02/03 03/14/05 Josh DONE<br /> 1205 02/09/03 Josh PENDING<br /> 1206 02/16/03 Josh PENDING<br /> 1207 02/23/03 Josh PENDING<br /> 1208 03/02/03 02/26/05 Josh ALMOST CLEAN<br /> 1209 03/09/03 02/26/05 Josh ALMOST CLEAN<br /> 1210 03/16/03 02/26/05 Josh NEEDS CLEAN<br /> 1211 03/23/03 02/27/05 Josh DONE<br /> 1212 03/30/03 02/26/05 Josh DONE<br /> 1213 04/06/03 03/12/05 Josh RUNNING<br /> 1214 04/13/03 02/26/05 Josh CLEANED<br /> 1215 04/20/03 02/27/05 Josh CLEANED<br /> 1216 04/27/03 02/26/05 Josh PENDING<br /> 1217 05/04/03 02/26/05 Josh NEEDS CLEAN<br /> 1218 05/11/03 02/27/05 Josh NEEDS CLEAN<br /> 1219 05/18/03 02/27/05 Josh WORKING<br /> 1220 05/25/03 02/27/05 Josh PENDING<br /> 1221 06/01/03 Josh PENDING<br /> 1222 06/08/03 Josh PENDING<br /> 1223 06/15/03 Josh PENDING<br /> 1224 06/22/03 Josh PENDING<br /> 1225 06/29/03 02/26/05 Josh FAILED<br /> 1226 07/06/03 02/26/05 Josh ALMOST CLEAN<br /> 1227 07/13/03 02/26/05 Josh FAILED<br /> 1228 07/20/03 Josh FAILED<br /> 1229 07/27/03 11/10/05 Tom Submitted <br /> 1230 08/03/03 Josh FAILED<br /> 1231 08/10/03 Josh FAILED<br /> 1232 08/17/03 11/10/05 Tom Submitted <br /> 1233 08/24/03 02/26/05 Josh ALMOST CLEAN<br /> 1234 08/31/03 02/26/05 Josh ALMOST CLEAN<br /> 1235 09/07/03 02/26/05 Josh ALMOST CLEAN<br /> 1236 09/14/03 02/26/05 Josh ALMOST CLEAN<br /> 1237 09/21/03 02/26/05 Josh NEEDS CLEAN<br /> 1238 09/28/03 02/26/05 Josh NEEDS CLEAN<br /> 1239 10/05/03 02/26/05 Josh WORKING<br /> 1240 10/12/03 02/26/05 Josh PENDING<br /> 1241 10/19/03 02/26/05 Josh NEEDS CLEAN<br /> 1242 10/26/03 02/26/05 Josh ALMOST CLEAN<br /> 1243 11/02/03 02/26/05 Josh NEEDS CLEAN<br /> 1244 11/09/03 02/26/05 Josh NEEDS CLEAN<br /> 1245 11/16/03 02/26/05 Josh ALMOST CLEAN<br /> 1246 11/23/03 02/26/05 Josh ALMOST CLEAN<br /> 1247 11/30/03 02/26/05 Josh ALMOST CLEAN<br /> 1248 12/07/03 02/26/05 Josh NEEDS CLEAN<br /> 1249 12/14/03 02/26/05 Josh NEEDS CLEAN<br /> 1250 12/21/03 02/26/05 Josh NEEDS CLEAN<br /> 1251 12/28/03 02/26/05 Josh WORKING<br /> <br /> ***************************2004*********************************<br /> <br /> 1253 01/11/04 02/26/05 Josh PENDING<br /> 1254 01/18/04 Josh PENDING<br /> 1255 01/25/04 Josh NEEDS<br /> 1256 02/01/04 Josh PENDING<br /> 1257 02/08/04 Josh PENDING<br /> 1258 02/15/04 Josh PENDING<br /> 1259 02/22/04 Josh PENDING<br /> 1260 02/29/04 Josh PENDING<br /> 1261 03/07/04 02/26/05 Josh PENDING<br /> 1262 03/14/04 02/26/05 Josh NEEDS CLEAN<br /> 1263 03/21/04 02/26/05 Josh NEEDS CLEAN<br /> 1264 03/28/04 02/26/05 Josh NEEDS CLEAN<br /> 1265 04/04/04 02/26/05 Josh FAILED No files found, needs re<br /> run<br /> 1266 04/11/04 02/26/05 Josh FAILED No files found, needs re<br /> run<br /> 1267 04/18/04 02/26/05 Josh NEEDS CLEAN<br /> 1268 04/25/04 02/26/05 Josh NEEDS CLEAN<br /> 1269 05/02/04 02/26/05 Josh NEEDS CLEAN<br /> 1270 05/09/04 02/26/05 Josh NEEDS CLEAN<br /> 1271 05/16/04 02/26/05 Josh NEEDS CLEAN<br /> 1272 05/23/04 02/26/05 Josh NEEDS CLEAN<br /> 1273 05/30/04 02/26/05 Josh NEEDS CLEAN<br /> 1274 06/06/04 02/26/05 Josh NEEDS CLEAN<br /> 1275 06/13/04 02/26/05 Josh NEEDS CLEAN<br /> 1276 06/20/04 02/27/05 Samik DONE<br /> 1277 06/27/04 03/19/05 Jeff NEEDS CLEAN<br /> 1278 07/04/04 03/19/05 Jeff NEEDS CLEAN<br /> 1279 07/11/04 03/19/05 Jeff NEEDS CLEAN<br /> 1280 07/18/04 03/19/05 Jeff NEEDS CLEAN<br /> 1281 07/25/04 03/19/05 Jeff NEEDS CLEAN<br /> 1282 08/01/04 Josh PENDING<br /> 1283 08/08/04 Josh PENDING<br /> 1284 08/15/04 Josh PENDING<br /> 1285 08/22/04 Josh PENDING<br /> 1286 08/29/04 Josh PENDING<br /> 1287 09/05/04 Josh PENDING<br /> 1288 09/12/04 Josh PENDING<br /> 1289 09/19/04 03/19/05 Jeff ??<br /> 1290 09/26/04 Josh PENDING<br /> 1291 10/03/04 Josh PENDING<br /> 1292 10/10/04 03/19/05 Jeff ??<br /> 1293 10/17/04 Josh PENDING<br /> 1294 10/24/04 03/19/05 Jeff ??<br /> 1295 10/31/04 03/25/05 Tom CLEAN<br /> 1296 11/07/04 04/07/05 Tom Cleaning<br /> 1297 11/14/04 03/19/05 Jeff ??<br /> 1298 11/21/04 NEEDS CLEAN<br /> 1299 11/28/04 NEEDS CLEAN<br /> 1300 12/05/04 08/16/05 Pravee CLEAN<br /> 1301 12/12/04 08/19/05 Pravee CLEAN<br /> 1302 12/19/04 08/19/05 Pravee CLEAN trivikram(tibet) CLEAN 07/26/2006<br /> 1303 12/26/04 08/26/05 Pravee CLEAN <br /> </pre><br /> <br /> ===Archaic (pre-1996)===<br /> <pre><br /> week # start date last processed who status<br /> ****************************************************************<br /> At the moment, Jeff is dealing with these.<br /> </pre></div>

Yuning http://gps.alaska.edu/internal/index.php?title=WHOS&diff=591 WHOS 2008-07-03T20:22:56Z

<p>Yuning: /* Week Schedule as of 9/7/07 */</p> <hr /> <div>The WHOS list tracks assigned GPS weeks for processing.<br /> <br /> More details about analysis at [[GPS analysis system]].<br /> <br /> ===Recent weeks===<br /> <pre><br /> week # start date last processed who status<br /> ****************************************************************<br /> 1375 05/14/2006 Trivikram/trivikram 1/ CLEAN EXCEPT 2 DAYS<br /> 1376 05/21/2006 Trivikram/1-2/ CLEAN<br /> 1377 05/28/2006 07/20/2006 Trivikram 1<br /> 1378 06/04/2006 07/20/2006 Trivikram 1 <br /> 1379 06/11/2006 07/20/2006 Trivikram 1 <br /> 1380 06/18/2006 07/20/2006 Trivikram 1 <br /> 1381 06/25/2006 07/12/2006 Ryan<br /> 1382 07/02/2006 Julie<br /> 1383 07/09/2006 Julie<br /> 1384 07/16/2006 Julie<br /> 1385 07/23/2006 Julie<br /> <br /> 1413 02/04/2007 05/01/2007 Tom<br /> </pre><br /> ===Week Schedule as of 9/7/07===<br /> <pre><br /> week # start date last processed who status<br /> *************************************************************<br /> 1430 Brandon NEAsia Alaska and NOAM-clean<br /> <br /> 1431 09/??/2007 10/31/2007 Lissy AK - clean<br /> 1431 11/05/2007 01/??/2008 Lissy initial cleaning done for Tibet solution<br /> 1431 01/09/2008 Lissy Casa solutions started<br /> <br /> 1432 Yuning initial cleaning done<br /> 1433 09/14/2007 09/26/2007 Ronni 1st iteration <br /> 1434 Julie<br /> 1435 Julie<br /> 1436 Julie<br /> 1437 Julie<br /> 1438 Julie<br /> 1439 Brandon one more iteration<br /> 1440 12?/??/2007 Lissy<br /> 1441 Yuning initial cleaning done<br /> 1442 09/27/2007 Ronni initial cleaning done<br /> 1443 Brandon NEA clean<br /> 1444 01/16/2008 Lissy<br /> 1445 Yuning initial cleaning done<br /> 1446 03/11/2008 Ronni<br /> 1447 Brandon initial cleaning done<br /> 1448 11/16/2007 05/12/2008 Lissy initial cleaning done<br /> 1449 Brandon NEA and Alaska cleaned<br /> 1450 Brandon initial cleaning done<br /> 1451 Brandon initial cleaning done<br /> 1452 01/23/2008 01/28/2008 Lissy initial cleaning done for Tibet & casa solution <br /> 1453 Yuning initial cleaning done<br /> 1454 05/05/2008 Ronni AK first interation<br /> 1455 Brandon initial cleaning done<br /> 1456 01/28/2008 Lissy<br /> 1457 Yuning initial cleaning done<br /> 1458 05/05/2008 Ronni AK first interation<br /> 1459 Julie<br /> 1460 Brandon NEA and AK cleaned<br /> 1461 02/06/2008 Lissy<br /> 1462 Yuning initial cleaning done<br /> 1463 05/05/2008 Ronni AK first interation<br /> 1464 Julie<br /> 1465 Brandon initial cleaning done<br /> 1466 04/09/2008 Lissy<br /> 1467 Yuning AK cleaning done<br /> 1468 05/05/2008 Ronni AK first interation<br /> 1469 Julie<br /> 1470 Brandon initial cleaning done<br /> 1471 04/09/2008 Lissy<br /> 1472 Yuning AK cleaning done<br /> 1473 05/05/2008 Ronni AK first interation<br /> 1474 Julie<br /> 1475 Brandon<br /> 1476 Lissy<br /> 1477 Yuning<br /> 1478 05/05/2008 Ronni AK first interation<br /> 1479 Julie<br /> 1480 Brandon<br /> 1481 Lissy<br /> 1482 Yuning<br /> 1483 Ronni<br /> 1484 Julie<br /> 1485 Brandon<br /> 1486 Lissy<br /> 1487 Yuning<br /> 1488 Ronni<br /> 1489 Julie<br /> 1490 Brandon<br /> 1491 Lissy<br /> 1492 Yuning<br /> 1493 Ronni<br /> 1494 Julie<br /> 1495 Brandon<br /> 1496 Lissy<br /> 1497 Yuning<br /> 1498 Ronni<br /> 1499 Julie<br /> 1500 Brandon<br /> <br /> </pre><br /> <br /> ===2006===<br /> <pre><br /> week # start date last processed who status<br /> ****************************************************************<br /> 1357 01/08/2006 Sandeep CLEANING Venkat<br /> 1358 01/15/2006 Sandeep CLEANING Venkat<br /> 1359 01/22/2006 Sandeep CLEAN Venkat (AK Point File Size < 300)<br /> 1360 01/29/2006 Sandeep CLEANING Venkat<br /> 1361 02/05/2006 Trivikram<br /> 1362 02/12/2006 Trivikram CLEAN (AK Point file size < 400)<br /> 1363 02/19/2006 Venkat CLEAN (AK Point file size < 400)<br /> 1364 02/26/2006 Trivikram<br /> 1365 03/05/2006 Venkat CLEANING <br /> 1366 03/12/2006 Trivikram<br /> 1367 03/19/2006 Trivikram <br /> 1368 03/26/2006 Trivikram problem with AK CLEANING SOLN<br /> 1369 04/02/2006 Trivikram CLEAN<br /> 1370 04/09/2006 Tom <br /> 1371 04/16/2006 Venkat CLEANING<br /> 1372 04/23/2006 Venkat CLEANING <br /> 1373 04/30/2006 Venkat CLEANING<br /> 1374 05/07/2006 Venkat CLEANING<br /> </pre><br /> <br /> ===2005===<br /> <pre><br /> week # start date last processed who status<br /> ****************************************************************<br /> 1304 01/02/2005 09/16/2005 Ryan CLEAN<br /> 1305 01/09/2005 08/30/2005 Pravee CLEAN<br /> 1306 01/16/2005 07/15/2005 Jill WORKING Trivikram(tibet) 07/26/2006 CLEAN<br /> 1307 01/23/2005 08/31/2005 Pravee CLEAN Trivikram(tibet) 07/26/2006 CLEAN<br /> 1308 01/30/2005 04/05/2005 Jill CLEAN Trivikram(tibet) 07/26/2006 CLEAN<br /> 1309 02/06/2005 08/31/2005 Pravee CLEAN <br /> 1310 02/13/2005 03/12/2005 Julie CLEAN <br /> 1311 02/20/2005 03/12/2005 Pravee CLEANING<br /> 1312 02/27/2005 03/31/2005 Tom CLEAN<br /> 1313 03/06/2005 03/31/2005 Pravee CLEANING<br /> 1314 03/13/2005 03/31/2005 Tom CLEAN<br /> 1315 03/20/2005 06/13/2005 Samik CLEAN (Point File Size < 500)<br /> 1316 03/27/2005 06/13/2005 Samik CLEAN (Point File Size < 400) <br /> 1317 04/03/2005 06/16/2005 Samik CLEAN (Point File Size < 400)<br /> 1318 04/10/2005 9/15/2005 Ryan not sure what's going on?<br /> 1319 04/17/2005 10/4/2005 Ryan ak SUBMITTED<br /> 1320 04/24/2005 Sandeep Done 1 2 Trivikram(tibet) 07/27/2006 1 2 CLEAN except 2 days<br /> 1321 05/01/2005 Sandeep Done 1 2 Trivikram(tibet) 07/28/2006 1 <br /> 1322 05/08/2005 Sandeep Done 1 2 Trivikram(tibet) 07/28/2006 1<br /> 1323 05/15/2005 Sandeep Done 1 2 Trivikram(tibet) 08/04/2006 1 <br /> 1324 05/22/2005 Sandeep Done 1 2 Trivikram(tibet) 08/04/2006 1<br /> 1325 05/29/2005 Sigrun DONE Trivikram(tibet) 08/04/2006 1<br /> 1326 06/05/2005 Sigrun DONE Trivikram(tibet) 08/06/2006 1<br /> 1327 06/12/2005 Sandeep Done 1 2 NO TIBET<br /> 1328 06/19/2005 Sandeep Done 1 2 No TIBET<br /> 1329 06/26/2005 Sandeep Done 1 2 Trivikram(tibet) 08/18/2006 1<br /> 1330 07/03/2005 9/14/2005 Ryan DONE<br /> 1331 07/10/2005 11/10/2005 Tom Submitted<br /> 1332 07/17/2005 Sandeep CLEAN Venkat (AK Point File Size < 500)<br /> 1333 07/24/2005 Sandeep CLEAN Trivikram <br /> 1334 07/31/2005 Sandeep CLEAN Trivikram <br /> 1335 08/07/2005 9/12/2005 Tom CLEAN Venkat (AK Point File Size < 400)<br /> 1336 08/14/2005 Sandeep CLEAN Venkat (AK Point File Size < 300)<br /> 1337 08/21/2005 10/17/2005 Ryan ak CLEAN Venkat (AK Point File Size < 300) <br /> 1338 08/28/2005 10/17/2005 Ryan ak CLEAN Venkat (AK Point File Size < 300) <br /> 1339 09/04/2005 11/08/2005 Ryan CLEAN Trivikram (AK Point File Size < 300) <br /> 1340 09/11/2005 Sandeep CLEAN Venkat (AK Point File Size < 300)<br /> 1341 09/18/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1342 09/25/2005 Sandeep CLEAN Venkat (AK Point File Size < 300) <br /> 1343 10/02/2005 Sandeep CLEAN Venkat (AK Point File Size < 300)<br /> 1344 10/09/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1345 10/16/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1346 10/23/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1347 10/30/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1348 11/06/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1349 11/13/2005 Sandeep CLEAN Venkat (AK Point File Size < 300) <br /> 1350 11/20/2005 Sandeep CLEAN Venkat (AK Point File Size < 400) <br /> 1351 11/27/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1352 12/04/2005 Sandeep CLEAN Venkat (AK Point File Size < 300) <br /> 1353 12/11/2005 Sandeep CLEAN Venkat (AK Point File Size < 400)<br /> 1354 12/18/2005 Sandeep CLEANING Venkat<br /> 1356 12/25/2005 Sandeep CLEANING Venkat<br /> </pre><br /> <br /> ===Older Stuff===<br /> <pre><br /> week # start date last processed who status<br /> ****************************************************************<br /> ****************************************************************<br /> ***************************2002*********************************<br /> **************************EARTHQUAKE****************************<br /> 1189 10/20/02 02/26/05 Josh PENDING<br /> 1190 10/27/02 Josh PENDING<br /> 1191 11/03/02 03/04/05 Josh DONE<br /> 1192 11/10/02 03/11/05 Josh DONE<br /> 1193 11/17/02 03/11/05 Josh DONE<br /> 1194 11/24/02 03/11/05 Josh DONE<br /> 1195 12/01/02 03/11/05 Josh RUNNING<br /> 1196 12/08/02 03/11/05 Josh DONE<br /> 1197 12/15/02 03/11/05 Josh DONE<br /> 1198 12/22/02 03/12/05 Josh DONE<br /> 1199 12/29/02 03/12/05 Josh DONE<br /> <br /> *************************2003***********************************<br /> <br /> 1200 01/05/03 03/12/05 Josh DONE<br /> 1201 01/12/03 03/12/05 Josh DONE<br /> 1202 01/19/03 03/15/05 Josh RUNNING<br /> 1203 01/26/03 03/14/05 Josh DONE<br /> 1204 02/02/03 03/14/05 Josh DONE<br /> 1205 02/09/03 Josh PENDING<br /> 1206 02/16/03 Josh PENDING<br /> 1207 02/23/03 Josh PENDING<br /> 1208 03/02/03 02/26/05 Josh ALMOST CLEAN<br /> 1209 03/09/03 02/26/05 Josh ALMOST CLEAN<br /> 1210 03/16/03 02/26/05 Josh NEEDS CLEAN<br /> 1211 03/23/03 02/27/05 Josh DONE<br /> 1212 03/30/03 02/26/05 Josh DONE<br /> 1213 04/06/03 03/12/05 Josh RUNNING<br /> 1214 04/13/03 02/26/05 Josh CLEANED<br /> 1215 04/20/03 02/27/05 Josh CLEANED<br /> 1216 04/27/03 02/26/05 Josh PENDING<br /> 1217 05/04/03 02/26/05 Josh NEEDS CLEAN<br /> 1218 05/11/03 02/27/05 Josh NEEDS CLEAN<br /> 1219 05/18/03 02/27/05 Josh WORKING<br /> 1220 05/25/03 02/27/05 Josh PENDING<br /> 1221 06/01/03 Josh PENDING<br /> 1222 06/08/03 Josh PENDING<br /> 1223 06/15/03 Josh PENDING<br /> 1224 06/22/03 Josh PENDING<br /> 1225 06/29/03 02/26/05 Josh FAILED<br /> 1226 07/06/03 02/26/05 Josh ALMOST CLEAN<br /> 1227 07/13/03 02/26/05 Josh FAILED<br /> 1228 07/20/03 Josh FAILED<br /> 1229 07/27/03 11/10/05 Tom Submitted <br /> 1230 08/03/03 Josh FAILED<br /> 1231 08/10/03 Josh FAILED<br /> 1232 08/17/03 11/10/05 Tom Submitted <br /> 1233 08/24/03 02/26/05 Josh ALMOST CLEAN<br /> 1234 08/31/03 02/26/05 Josh ALMOST CLEAN<br /> 1235 09/07/03 02/26/05 Josh ALMOST CLEAN<br /> 1236 09/14/03 02/26/05 Josh ALMOST CLEAN<br /> 1237 09/21/03 02/26/05 Josh NEEDS CLEAN<br /> 1238 09/28/03 02/26/05 Josh NEEDS CLEAN<br /> 1239 10/05/03 02/26/05 Josh WORKING<br /> 1240 10/12/03 02/26/05 Josh PENDING<br /> 1241 10/19/03 02/26/05 Josh NEEDS CLEAN<br /> 1242 10/26/03 02/26/05 Josh ALMOST CLEAN<br /> 1243 11/02/03 02/26/05 Josh NEEDS CLEAN<br /> 1244 11/09/03 02/26/05 Josh NEEDS CLEAN<br /> 1245 11/16/03 02/26/05 Josh ALMOST CLEAN<br /> 1246 11/23/03 02/26/05 Josh ALMOST CLEAN<br /> 1247 11/30/03 02/26/05 Josh ALMOST CLEAN<br /> 1248 12/07/03 02/26/05 Josh NEEDS CLEAN<br /> 1249 12/14/03 02/26/05 Josh NEEDS CLEAN<br /> 1250 12/21/03 02/26/05 Josh NEEDS CLEAN<br /> 1251 12/28/03 02/26/05 Josh WORKING<br /> <br /> ***************************2004*********************************<br /> <br /> 1253 01/11/04 02/26/05 Josh PENDING<br /> 1254 01/18/04 Josh PENDING<br /> 1255 01/25/04 Josh NEEDS<br /> 1256 02/01/04 Josh PENDING<br /> 1257 02/08/04 Josh PENDING<br /> 1258 02/15/04 Josh PENDING<br /> 1259 02/22/04 Josh PENDING<br /> 1260 02/29/04 Josh PENDING<br /> 1261 03/07/04 02/26/05 Josh PENDING<br /> 1262 03/14/04 02/26/05 Josh NEEDS CLEAN<br /> 1263 03/21/04 02/26/05 Josh NEEDS CLEAN<br /> 1264 03/28/04 02/26/05 Josh NEEDS CLEAN<br /> 1265 04/04/04 02/26/05 Josh FAILED No files found, needs re<br /> run<br /> 1266 04/11/04 02/26/05 Josh FAILED No files found, needs re<br /> run<br /> 1267 04/18/04 02/26/05 Josh NEEDS CLEAN<br /> 1268 04/25/04 02/26/05 Josh NEEDS CLEAN<br /> 1269 05/02/04 02/26/05 Josh NEEDS CLEAN<br /> 1270 05/09/04 02/26/05 Josh NEEDS CLEAN<br /> 1271 05/16/04 02/26/05 Josh NEEDS CLEAN<br /> 1272 05/23/04 02/26/05 Josh NEEDS CLEAN<br /> 1273 05/30/04 02/26/05 Josh NEEDS CLEAN<br /> 1274 06/06/04 02/26/05 Josh NEEDS CLEAN<br /> 1275 06/13/04 02/26/05 Josh NEEDS CLEAN<br /> 1276 06/20/04 02/27/05 Samik DONE<br /> 1277 06/27/04 03/19/05 Jeff NEEDS CLEAN<br /> 1278 07/04/04 03/19/05 Jeff NEEDS CLEAN<br /> 1279 07/11/04 03/19/05 Jeff NEEDS CLEAN<br /> 1280 07/18/04 03/19/05 Jeff NEEDS CLEAN<br /> 1281 07/25/04 03/19/05 Jeff NEEDS CLEAN<br /> 1282 08/01/04 Josh PENDING<br /> 1283 08/08/04 Josh PENDING<br /> 1284 08/15/04 Josh PENDING<br /> 1285 08/22/04 Josh PENDING<br /> 1286 08/29/04 Josh PENDING<br /> 1287 09/05/04 Josh PENDING<br /> 1288 09/12/04 Josh PENDING<br /> 1289 09/19/04 03/19/05 Jeff ??<br /> 1290 09/26/04 Josh PENDING<br /> 1291 10/03/04 Josh PENDING<br /> 1292 10/10/04 03/19/05 Jeff ??<br /> 1293 10/17/04 Josh PENDING<br /> 1294 10/24/04 03/19/05 Jeff ??<br /> 1295 10/31/04 03/25/05 Tom CLEAN<br /> 1296 11/07/04 04/07/05 Tom Cleaning<br /> 1297 11/14/04 03/19/05 Jeff ??<br /> 1298 11/21/04 NEEDS CLEAN<br /> 1299 11/28/04 NEEDS CLEAN<br /> 1300 12/05/04 08/16/05 Pravee CLEAN<br /> 1301 12/12/04 08/19/05 Pravee CLEAN<br /> 1302 12/19/04 08/19/05 Pravee CLEAN trivikram(tibet) CLEAN 07/26/2006<br /> 1303 12/26/04 08/26/05 Pravee CLEAN <br /> </pre><br /> <br /> ===Archaic (pre-1996)===<br /> <pre><br /> week # start date last processed who status<br /> ****************************************************************<br /> At the moment, Jeff is dealing with these.<br /> </pre></div>

Yuning http://gps.alaska.edu/internal/index.php?title=RoiPac&diff=594 RoiPac 2008-07-03T01:31:46Z

<p>Yuning: /* Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC. */</p> <hr /> <div>Our lab has installed ROI_PAC 3.0 for SAR and InSAR processing. Some detailed introductions and explainations will be followed soon. And also, you can get information about InSAR and ROI_PAC from the links below.<br /> <br /> http://roipac.org/<br /> <br /> http://www.uoregon.edu/~das/WikiRoiPac/doku.php?id=welcome<br /> <br /> === ROI_PAC ===<br /> <br /> ROI_PAC is located at /usr/local/ROI_PAC_3_0, and there is also SAR data available for your test at /usr/local/TEST_DIR directory. More information about how to play with it will be updated soon.<br /> <br /> ===Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC.===<br /> <br /> Take the test data (/usr/local/TEST_DIR) for example to explain the processing.<br /> <br /> First, compile some environment variable and path used by ROI_PCA. There is already a template file named SAR_CONFIG at /usr/local/ROI_PAC_3_0/ROI_PAC. Change the necessary commands, and then "source" in.<br /> <br /> source SAR_CONFIG<br /> <br /> <br /> Then, ingest the data. Go to the SAR data directory (/usr/local/TEST_DIR/930110 and /usr/local/TEST_DIR/950523), and ingest data respectively. <br /> <br /> TEST_DIR/930110> make_raw.pl PRC SARLEADER1993011018252739T1Of1 930110 <br /> TEST_DIR/950523> make_raw.pl PRC SARLEADER1995052318253409T1Of1 950523 <br /> <br /> Note: Different SAR data format has different commands to ingest. For our case, they are ERS data, so "make_raw.pl" is used.<br /> <br /> Last, data processing. Actually, there is a command "process_2pass.pl" can run all the steps after raw data ready. And the file "int.proc" in main directory (/usr/local/TEST_DIR) specifiles two scene directories (data and orbit) and other processing parameters for a given interferogram.<br /> <br /> process_2pass.pl int.proc<br /> <br /> And also, we can do it step by step.<br /> <br /> process_2pass.pl int.proc [DoItFrom EndItAt]<br /> <br /> DoItFrom = point in process.pl to start<br /> EndItAt = point in process.pl to end<br /> Can be: raw, roi_prep, orbbase, slcs, offsets, resamp, flatorb, full_res, filtered, make_mask, unwrapped, simulation, morph_sim, <br /> redo_base or use_sim_base<br /> EndItAt can also be synth_offset<br /> <br /> For more information about ROI_PAC, please refer POI_PAC [http://roipac.org/ website] and Eric Fielding's ppt [http://gps.alaska.edu/~yuning/Eric_Roipac.ppt "ROI-pac Internals"].</div>

Yuning http://gps.alaska.edu/internal/index.php?title=RoiPac&diff=589 RoiPac 2008-07-03T01:31:18Z

<p>Yuning: /* Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC. */</p> <hr /> <div>Our lab has installed ROI_PAC 3.0 for SAR and InSAR processing. Some detailed introductions and explainations will be followed soon. And also, you can get information about InSAR and ROI_PAC from the links below.<br /> <br /> http://roipac.org/<br /> <br /> http://www.uoregon.edu/~das/WikiRoiPac/doku.php?id=welcome<br /> <br /> === ROI_PAC ===<br /> <br /> ROI_PAC is located at /usr/local/ROI_PAC_3_0, and there is also SAR data available for your test at /usr/local/TEST_DIR directory. More information about how to play with it will be updated soon.<br /> <br /> ===Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC.===<br /> <br /> Take the test data (/usr/local/TEST_DIR) for example to explain the processing.<br /> <br /> First, compile some environment variable and path used by ROI_PCA. There is already a template file named SAR_CONFIG at /usr/local/ROI_PAC_3_0/ROI_PAC. Change the necessary commands, and then "source" in.<br /> <br /> source SAR_CONFIG<br /> <br /> <br /> Then, ingest the data. Go to the SAR data directory (/usr/local/TEST_DIR/930110 and /usr/local/TEST_DIR/950523), and ingest data respectively. <br /> <br /> TEST_DIR/930110> make_raw.pl PRC SARLEADER1993011018252739T1Of1 930110 <br /> TEST_DIR/950523> make_raw.pl PRC SARLEADER1995052318253409T1Of1 950523 <br /> <br /> Note: Different SAR data format has different commands to ingest. For our case, they are ERS data, so "make_raw.pl" is used.<br /> <br /> Last, data processing. Actually, there is a command "process_2pass.pl" can run all the steps after raw data ready. And the file "int.proc" in main directory (/usr/local/TEST_DIR) specifiles two scene directories (data and orbit) and other processing parameters for a given interferogram.<br /> <br /> process_2pass.pl int.proc<br /> <br /> And also, we can do it step by step.<br /> <br /> process_2pass.pl int.proc [DoItFrom EndItAt]<br /> <br /> DoItFrom = point in process.pl to start<br /> EndItAt = point in process.pl to end<br /> Can be: raw, roi_prep, orbbase, slcs, offsets, resamp, flatorb, full_res, filtered, make_mask, unwrapped, simulation, morph_sim, <br /> redo_base or use_sim_base<br /> EndItAt can also be synth_offset<br /> <br /> For more information about ROI_PAC, please refer POI_PAC [http://roipac.org/ website] and Eric Fielding's ppt [http://gps.alaska.edu/~yuning/Eric_Roipac.ppt "ROI_pac Internals"].</div>

Yuning http://gps.alaska.edu/internal/index.php?title=RoiPac&diff=588 RoiPac 2008-07-03T01:27:21Z

<p>Yuning: /* Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC. */</p> <hr /> <div>Our lab has installed ROI_PAC 3.0 for SAR and InSAR processing. Some detailed introductions and explainations will be followed soon. And also, you can get information about InSAR and ROI_PAC from the links below.<br /> <br /> http://roipac.org/<br /> <br /> http://www.uoregon.edu/~das/WikiRoiPac/doku.php?id=welcome<br /> <br /> === ROI_PAC ===<br /> <br /> ROI_PAC is located at /usr/local/ROI_PAC_3_0, and there is also SAR data available for your test at /usr/local/TEST_DIR directory. More information about how to play with it will be updated soon.<br /> <br /> ===Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC.===<br /> <br /> Take the test data (/usr/local/TEST_DIR) for example to explain the processing.<br /> <br /> First, compile some environment variable and path used by ROI_PCA. There is already a template file named SAR_CONFIG at /usr/local/ROI_PAC_3_0/ROI_PAC. Change the necessary commands, and then "source" in.<br /> <br /> source SAR_CONFIG<br /> <br /> <br /> Then, ingest the data. Go to the SAR data directory (/usr/local/TEST_DIR/930110 and /usr/local/TEST_DIR/950523), and ingest data respectively. <br /> <br /> TEST_DIR/930110> make_raw.pl PRC SARLEADER1993011018252739T1Of1 930110 <br /> TEST_DIR/950523> make_raw.pl PRC SARLEADER1995052318253409T1Of1 950523 <br /> <br /> Note: Different SAR data format has different commands to ingest. For our case, they are ERS data, so "make_raw.pl" is used.<br /> <br /> Last, data processing. Actually, there is a command "process_2pass.pl" can run all the steps after raw data ready. And the file "int.proc" in main directory (/usr/local/TEST_DIR) specifiles two scene directories (data and orbit) and other processing parameters for a given interferogram.<br /> <br /> process_2pass.pl int.proc<br /> <br /> And also, we can do it step by step.<br /> <br /> process_2pass.pl int.proc [DoItFrom EndItAt]<br /> <br /> DoItFrom = point in process.pl to start<br /> EndItAt = point in process.pl to end<br /> Can be: raw, roi_prep, orbbase, slcs, offsets, resamp, flatorb, full_res, filtered, make_mask, unwrapped, simulation, morph_sim, <br /> redo_base or use_sim_base<br /> EndItAt can also be synth_offset<br /> <br /> For more information about ROI_PAC, please refer POI_PAC [http://roipac.org/ website] and Eric Fielding's ppt .</div>

Yuning http://gps.alaska.edu/internal/index.php?title=RoiPac&diff=587 RoiPac 2008-07-03T01:22:38Z

<p>Yuning: /* Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC. */</p> <hr /> <div>Our lab has installed ROI_PAC 3.0 for SAR and InSAR processing. Some detailed introductions and explainations will be followed soon. And also, you can get information about InSAR and ROI_PAC from the links below.<br /> <br /> http://roipac.org/<br /> <br /> http://www.uoregon.edu/~das/WikiRoiPac/doku.php?id=welcome<br /> <br /> === ROI_PAC ===<br /> <br /> ROI_PAC is located at /usr/local/ROI_PAC_3_0, and there is also SAR data available for your test at /usr/local/TEST_DIR directory. More information about how to play with it will be updated soon.<br /> <br /> ===Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC.===<br /> <br /> Take the test data (/usr/local/TEST_DIR) for example to explain the processing.<br /> <br /> First, compile some environment variable and path used by ROI_PCA. There is already a template file named SAR_CONFIG at /usr/local/ROI_PAC_3_0/ROI_PAC. Change the necessary commands, and then "source" in.<br /> <br /> source SAR_CONFIG<br /> <br /> <br /> Then, ingest the data. Go to the SAR data directory (/usr/local/TEST_DIR/930110 and /usr/local/TEST_DIR/950523), and ingest data respectively. <br /> <br /> TEST_DIR/930110> make_raw.pl PRC SARLEADER1993011018252739T1Of1 930110 <br /> TEST_DIR/950523> make_raw.pl PRC SARLEADER1995052318253409T1Of1 950523 <br /> <br /> Note: Different SAR data format has different commands to ingest. For our case, they are ERS data, so "make_raw.pl" is used.<br /> <br /> Last, data processing. Actually, there is a command "process_2pass.pl" can run all the steps after raw data ready. And the file "int.proc" in main directory (/usr/local/TEST_DIR) specifiles two scene directories (data and orbit) and other processing parameters for a given interferogram.<br /> <br /> process_2pass.pl int.proc<br /> <br /> And also, we can do it step by step.<br /> <br /> process_2pass.pl int.proc [DoItFrom EndItAt]<br /> <br /> DoItFrom = point in process.pl to start<br /> EndItAt = point in process.pl to end<br /> Can be: raw, roi_prep, orbbase, slcs, offsets, resamp, flatorb, full_res, filtered, make_mask, unwrapped, simulation, morph_sim, <br /> redo_base or use_sim_base<br /> EndItAt can also be synth_offset<br /> <br /> For more information about ROI_PAC, please refer POI_PAC website and Eric Fielding's ppt "POI_pac Internals".</div>

Yuning http://gps.alaska.edu/internal/index.php?title=RoiPac&diff=586 RoiPac 2008-07-03T01:17:50Z

<p>Yuning: /* Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC. */</p> <hr /> <div>Our lab has installed ROI_PAC 3.0 for SAR and InSAR processing. Some detailed introductions and explainations will be followed soon. And also, you can get information about InSAR and ROI_PAC from the links below.<br /> <br /> http://roipac.org/<br /> <br /> http://www.uoregon.edu/~das/WikiRoiPac/doku.php?id=welcome<br /> <br /> === ROI_PAC ===<br /> <br /> ROI_PAC is located at /usr/local/ROI_PAC_3_0, and there is also SAR data available for your test at /usr/local/TEST_DIR directory. More information about how to play with it will be updated soon.<br /> <br /> ===Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC.===<br /> <br /> Take the test data (/usr/local/TEST_DIR) for example to explain the processing.<br /> <br /> First, compile some environment variable and path used by ROI_PCA. There is already a template file named SAR_CONFIG at /usr/local/ROI_PAC_3_0/ROI_PAC. Change the necessary commands, and then "source" in.<br /> <br /> source SAR_CONFIG<br /> <br /> <br /> Then, ingest the data. Go to the SAR data directory (/usr/local/TEST_DIR/930110 and /usr/local/TEST_DIR/950523), and ingest data respectively. <br /> <br /> TEST_DIR/930110> make_raw.pl PRC SARLEADER1993011018252739T1Of1 930110 <br /> TEST_DIR/950523> make_raw.pl PRC SARLEADER1995052318253409T1Of1 950523 <br /> <br /> Note: Different SAR data format has different commands to ingest. For our case, they are ERS data, so "make_raw.pl" is used.<br /> <br /> Last, data processing. Actually, there is a command "process_2pass.pl" can run all the steps after raw data ready. And the file "int.proc" in main directory (/usr/local/TEST_DIR) specifiles two scene directories (data and orbit) and other processing parameters for a given interferogram.<br /> <br /> process_2pass.pl int.proc<br /> <br /> And also, we can do it step by step.<br /> <br /> process_2pass.pl int.proc [DoItFrom EndItAt]<br /> <br /> DoItFrom = point in process.pl to start<br /> EndItAt = point in process.pl to end<br /> Can be: raw, roi_prep, orbbase, slcs, offsets, resamp, flatorb, full_res, filtered, make_mask, unwrapped, simulation, morph_sim, redo_base or use_sim_base<br /> EndItAt can also be synth_offset<br /> <br /> For more information about ROI_PAC, please refer POI_PAC website and Eric Fielding's ppt "POI_pac Internals".</div>

Yuning http://gps.alaska.edu/internal/index.php?title=RoiPac&diff=585 RoiPac 2008-07-03T01:14:08Z

<p>Yuning: /* Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC. */</p> <hr /> <div>Our lab has installed ROI_PAC 3.0 for SAR and InSAR processing. Some detailed introductions and explainations will be followed soon. And also, you can get information about InSAR and ROI_PAC from the links below.<br /> <br /> http://roipac.org/<br /> <br /> http://www.uoregon.edu/~das/WikiRoiPac/doku.php?id=welcome<br /> <br /> === ROI_PAC ===<br /> <br /> ROI_PAC is located at /usr/local/ROI_PAC_3_0, and there is also SAR data available for your test at /usr/local/TEST_DIR directory. More information about how to play with it will be updated soon.<br /> <br /> ===Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC.===<br /> <br /> Take the test data (/usr/local/TEST_DIR) for example to explain the processing.<br /> <br /> First, compile some environment variable and path used by ROI_PCA. There is already a template file named SAR_CONFIG at /usr/local/ROI_PAC_3_0/ROI_PAC. Change the necessary commands, and then "source" in.<br /> <br /> source SAR_CONFIG<br /> <br /> <br /> Then, ingest the data. Go to the SAR data directory (/usr/local/TEST_DIR/930110 and /usr/local/TEST_DIR/950523), and ingest data respectively. <br /> <br /> TEST_DIR/930110> make_raw.pl PRC SARLEADER1993011018252739T1Of1 930110 <br /> TEST_DIR/950523> make_raw.pl PRC SARLEADER1995052318253409T1Of1 950523 <br /> <br /> Note: Different SAR data format has different commands to ingest. For our case, they are ERS data, so "make_raw.pl" is used.<br /> <br /> Last, data processing. Actually, there is a command "process_2pass.pl" can run all the steps after raw data ready. And the file "int.proc" in main directory (/usr/local/TEST_DIR) specifiles two scene directories (data and orbit) and other processing parameters for a given interferogram.<br /> <br /> process_2pass.pl int.proc<br /> <br /> And also, we can do it step by step.<br /> <br /> process_2pass.pl int.proc [DoItFrom EndItAt]<br /> <br /> DoItFrom = point in process.pl to start<br /> EndItAt = point in process.pl to end<br /> Can be: raw, roi_prep, orbbase, slcs, offsets, resamp, flatorb, full_res, filtered, make_mask, unwrapped, simulation, morph_sim, redo_base or use_sim_base<br /> EndItAt can also be synth_offset</div>

Yuning http://gps.alaska.edu/internal/index.php?title=RoiPac&diff=584 RoiPac 2008-07-03T01:07:19Z

<p>Yuning: /* Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC. */</p> <hr /> <div>Our lab has installed ROI_PAC 3.0 for SAR and InSAR processing. Some detailed introductions and explainations will be followed soon. And also, you can get information about InSAR and ROI_PAC from the links below.<br /> <br /> http://roipac.org/<br /> <br /> http://www.uoregon.edu/~das/WikiRoiPac/doku.php?id=welcome<br /> <br /> === ROI_PAC ===<br /> <br /> ROI_PAC is located at /usr/local/ROI_PAC_3_0, and there is also SAR data available for your test at /usr/local/TEST_DIR directory. More information about how to play with it will be updated soon.<br /> <br /> ===Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC.===<br /> <br /> Take the test data (/usr/local/TEST_DIR) for example to explain the processing.<br /> <br /> First, compile some environment variable and path used by ROI_PCA. There is already a template file named SAR_CONFIG at /usr/local/ROI_PAC_3_0/ROI_PAC. Change the necessary commands, and then "source" in.<br /> <br /> source SAR_CONFIG<br /> <br /> <br /> Then, ingest the data. Go to the SAR data directory (/usr/local/TEST_DIR/930110 and /usr/local/TEST_DIR/950523), and ingest data respectively. <br /> <br /> TEST_DIR/930110> make_raw.pl PRC SARLEADER1993011018252739T1Of1 930110 <br /> TEST_DIR/950523> make_raw.pl PRC SARLEADER1995052318253409T1Of1 950523 <br /> <br /> Note: Different SAR data format has different commands to ingest. For our case, they are ERS data, so "make_raw.pl" is used.<br /> <br /> Last, data processing. Actually, there is a command "process_2pass.pl" can run all the steps after raw data ready. And the file "int.proc" in main directory (/usr/local/TEST_DIR) specifiles two scene directories (data and orbit) and other processing parameters for a given interferogram.<br /> <br /> process_2pass.pl int.proc<br /> <br /> And also,</div>

Yuning http://gps.alaska.edu/internal/index.php?title=RoiPac&diff=583 RoiPac 2008-07-03T00:59:40Z

<p>Yuning: /* Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC. */</p> <hr /> <div>Our lab has installed ROI_PAC 3.0 for SAR and InSAR processing. Some detailed introductions and explainations will be followed soon. And also, you can get information about InSAR and ROI_PAC from the links below.<br /> <br /> http://roipac.org/<br /> <br /> http://www.uoregon.edu/~das/WikiRoiPac/doku.php?id=welcome<br /> <br /> === ROI_PAC ===<br /> <br /> ROI_PAC is located at /usr/local/ROI_PAC_3_0, and there is also SAR data available for your test at /usr/local/TEST_DIR directory. More information about how to play with it will be updated soon.<br /> <br /> ===Usually, there are three steps to finish Interferometry SAR processing with ROI_PAC.===<br /> <br /> Take the test data (/usr/local/TEST_DIR) for example to explain the processing.<br /> <br /> First, compile some environment variable and path used by ROI_PCA. There is already a template file named SAR_CONFIG at /usr/local/ROI_PAC_3_0/ROI_PAC. Change the necessary commands, and then "source" in.<br /> <br /> source SAR_CONFIG<br /> <br /> <br /> Then, ingest the data. Go to the SAR data directory (/usr/local/TEST_DIR/930110 and /usr/local/TEST_DIR/950523), and ingest data respectively. <br /> <br /> TEST_DIR/930110> make_raw.pl PRC SARLEADER1993011018252739T1Of1 930110 <br /> TEST_DIR/950523> make_raw.pl PRC SARLEADER1995052318253409T1Of1 950523 <br /> <br /> Note: =Different SAR data format has different commands to ingest=. For our case, they are ERS data, so "make_raw.pl" is used.</div>

Yuning