====== Differences ====== This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
analysis:course:week1 [2013/09/20 15:55] jlocklin [For Linux users] |
analysis:course:week1 [2018/04/17 15:20] (current) |
||
|---|---|---|---|
| Line 67: | Line 67: | ||
| Use a FTP client such as [[https://filezilla-project.org/|Filezilla]] or ''WinSCP'' to connect to the lab FTP server, ''mvdmlab-nas1'' (129.97.62.84). Configure your FTP client to require "explicit FTP over TLS" and use ''BIOL680'' as username and password. In the ''BIOL680'' folder, download the folder ''R016-2012-10-08''. A good place to put this folder is in ''D:\data\promoted\R016\''. (In general you want to keep your data separate from your code; for instance, multiple analysis projects may use the same data, so you don't want to duplicate it.) | Use a FTP client such as [[https://filezilla-project.org/|Filezilla]] or ''WinSCP'' to connect to the lab FTP server, ''mvdmlab-nas1'' (129.97.62.84). Configure your FTP client to require "explicit FTP over TLS" and use ''BIOL680'' as username and password. In the ''BIOL680'' folder, download the folder ''R016-2012-10-08''. A good place to put this folder is in ''D:\data\promoted\R016\''. (In general you want to keep your data separate from your code; for instance, multiple analysis projects may use the same data, so you don't want to duplicate it.) | ||
| + | |||
| + | Correct FileZilla configuration is the following: | ||
| + | |||
| + | {{ :analysis:course:ftp_config.png?600 |}} | ||
| You will have to be on campus to connect. If you still cannot log in to the server, send me your IP address and I will temporarily enable access for you. IF it still does not work, get the .zip {{:analysis:course:r016-2012-10-08.zip|here}}. | You will have to be on campus to connect. If you still cannot log in to the server, send me your IP address and I will temporarily enable access for you. IF it still does not work, get the .zip {{:analysis:course:r016-2012-10-08.zip|here}}. | ||
| Line 120: | Line 124: | ||
| === Be backup-aware === | === Be backup-aware === | ||
| - | If you are using a lab computer, only put data and code on the ''D:\'' drive. This actually has two underlying hard drives (a [[http://en.wikipedia.org/wiki/RAID#RAID_1|RAID 1 array]] in "mirroring" mode) such that if one fails, your data is still available. However, this does not protect accidentally deleting data, overwriting a key file, any sort of data corruption or damage, //et cetera//. Some options to minimize the impact of those: | + | If you are using a lab computer, only put data and code on the ''D:\'' drive. This actually has two underlying hard drives (a [[http://en.wikipedia.org/wiki/RAID#RAID_1|RAID 1 array]] in "mirroring" mode) such that if one fails, your data is still available. However, this does not protect against accidentally deleting data, overwriting a key file, any sort of data corruption or damage, //et cetera//. Some options to minimize the impact of those: |
| * Save your code (and other work that does not take up huge amounts of space) on Dropbox, Google Drive, or similar service that keeps a (limited) revision history | * Save your code (and other work that does not take up huge amounts of space) on Dropbox, Google Drive, or similar service that keeps a (limited) revision history | ||