User Tools

Site Tools


analysis:course:week1

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
analysis:course:week1 [2013/09/20 11:48]
jlocklin [For Linux users]
analysis:course:week1 [2018/07/07 10:19] (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 106: Line 110:
  
  
-Follow the instructions above for Mac/OS X users, except you will have to recompile the binaries (note that you will probably ​need C and C++ compilers installed. Install the ''​build-essential''​ package on Ubuntu):+Follow the instructions above for Mac/OS X users, except you may need to recompile the binaries (note that you will need C and C++ compilers installed. Install the ''​build-essential''​ package on Ubuntu):
   * You may want to just delete the existing binaries.   * You may want to just delete the existing binaries.
   * Edit ''​compile.sh''​ to set ''​PLATFORM=64PC''​ or ''​PLATFORM=32PC''​ depending on your architecture,​ and edit INCLMATLAB and BINMATLAB so that they point to the correct directories for your Matlab installation. If you don't remember, run ''​locate mexsh''​ in the shell and you should see the path.   * Edit ''​compile.sh''​ to set ''​PLATFORM=64PC''​ or ''​PLATFORM=32PC''​ depending on your architecture,​ and edit INCLMATLAB and BINMATLAB so that they point to the correct directories for your Matlab installation. If you don't remember, run ''​locate mexsh''​ in the shell and you should see the path.
-  * You can rename all the files in the binary directory with <​code>​rename '​s/​_v3//'​ *</​code>​+  * You can rename all the files in the binary directory with the shell command: ​<code>> rename '​s/​_v3//'​ *</​code>​
  
 This worked on 64 bit Ubuntu with Matlab R2013b. This worked on 64 bit Ubuntu with Matlab R2013b.
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
analysis/course/week1.1379692136.txt.gz ยท Last modified: 2018/07/07 10:19 (external edit)