1. The Computers are always on. Never turn them off the Ever!
2. Exit programs correctly or they will remain running in the "background". This happens when progams are not properly exited before logging off. See"Accessing and Exiting RS/GIS LAB Programs".
3. Keep your door-entry code and passwords private. To not respect security measures could mean losing Lab privileges.
4. Save frequently, which is a good rule anyway since computers can crash! However, Unix computers are among the most stable and system issues which may cause problems will brought to the attention of students in as timely a manner as possible. Look for posted notices around the lab when you are there. Knowing the lab's schedule is the user's responsibility. Notice that the lab must accomodate multiple classes each semester.
5. Manually ejecting a CD to override the CD-ROM error message creates bigger problems. Remember to eject your CD before logging off. Do this by making sure you are in your home directory (/home/yourlogin) and then typing: eject cdrom Note: If any process is using the CD-ROM, eject will tell you it is busy and will not eject the CD. Once you quit the processes, the CD will eject.
6. If you make a mistake or think you have, tell someone in authority so they can bail you out (not beat you up!). Every one makes mistakes -- but no one profits if a mistake is left unattended. We want to help. .
7. Plan ahead. What is a crisis to you (I have to have this map today!) is not necessarily a crisis to the system administrator, your instructor, or other lab personnel. Besides, the day you need that important product is the day the system will probably go down. Don't Procrastinate!
8. Metadata: Always document your files with an associated text file. Include name. date, and source of the original data, conversion process, parent files, your name, your project, your project leader, and the date. Decide on a certain format and be consistent through out your database. Metadata insures the viability and credibility of your work.
9. Data Structure: The minimum data structure requirement for work done in the lab is a work directory and a final directory. In UNIX use the commands: mkdir work and mkdir final. All manipulation of data should be done in the work directory and final results should be copied and stored in the final directory. This makes it clear to instructors and end users what data is in process and which data is viable.
10. Always copy arc coverages in arc. using the command: copy . Never copy an arc coverage in UNIX, as your info files connected to the coverage will be lost.
11. Always delete arc coverages in arc using the command : Kill all. The all deletes the info file connected with the coverage. If you forget the all, use the command: Kill info
12. Understand projections, spheroids, and NAD and how they impact the final product. If there is a problem with a coverage, overlaying coverages, or output map, it is Likely due to a discrepancy among the three. IdeaLly, the projection, spheroid, and NAD should be identical for all coverages which will be overlaid or used in a single map project. Use the arc command: describe to determine any one of the three.
13. Understand the arc commands clean and build, when digitizing or editing arc coverages. Each performs similar tasks but clean is dangerous, whereas build is not. Lack of / knowledge about these two commands is a common source of data error in the lab.
14. Become familiar with the on-line lab notebook on the geography web site. Type netscape & at the UNIX prompt. When netscape appears on your screen (it takes a few seconds) type the address: http":www.nr.usu.edu/lab-book
15. For systems questions or problems use your e-mail tool and this address: bbanner@gis.usu.edu
16. If your computer is slow in responding, don't keep typing the command
or clicking the mouse. The workstation computer remembers every command
in order and executes them in order when the network traffic clears.