7
CMLAB Kickoff Meeting- Fall ‘10 1.) Weekly reporting 2.) Lab Meeting 3.) Computers and Accounts 4.) Backup policies 5.) Electronic lab notebook 6.) Demonstration: Setting up FVCOM, Running the model, and Post- processing results.

CMLAB Kickoff Meeting- Fall ‘10 1.) Weekly reporting 2.) Lab Meeting 3.) Computers and Accounts 4.) Backup policies 5.) Electronic lab notebook 6.) Demonstration:

Embed Size (px)

Citation preview

Page 1: CMLAB Kickoff Meeting- Fall ‘10 1.) Weekly reporting 2.) Lab Meeting 3.) Computers and Accounts 4.) Backup policies 5.) Electronic lab notebook 6.) Demonstration:

CMLAB Kickoff Meeting- Fall ‘10

1.) Weekly reporting2.) Lab Meeting3.) Computers and Accounts4.) Backup policies5.) Electronic lab notebook6.) Demonstration: Setting up FVCOM, Running the model, and Post-processing results.

Page 2: CMLAB Kickoff Meeting- Fall ‘10 1.) Weekly reporting 2.) Lab Meeting 3.) Computers and Accounts 4.) Backup policies 5.) Electronic lab notebook 6.) Demonstration:

Weekly ReportingPurpose: To Archive your work and let a busy advisor keep track of your progress

Reports are due Sunday night. Spend about 30 minutes putting it together.

Download the Latex Template from the following website

http://www.smast.umassd.edu/CMLAB/notebook/?page_id=16

Extract the tarfile, this will create the directory “PROGRESS_REPORTS”

Name your report on the Monday at the beginning of the week you are reporting.

Page 3: CMLAB Kickoff Meeting- Fall ‘10 1.) Weekly reporting 2.) Lab Meeting 3.) Computers and Accounts 4.) Backup policies 5.) Electronic lab notebook 6.) Demonstration:

Lab MeetingsFall 2010: Mondays from 10-12, 1st floor conference room.

• Discuss lab issues that effect everybody – IT, software problems• Demonstrations, Lectures, Paper discussions (led by students/staff), and presentations of results.

Page 4: CMLAB Kickoff Meeting- Fall ‘10 1.) Weekly reporting 2.) Lab Meeting 3.) Computers and Accounts 4.) Backup policies 5.) Electronic lab notebook 6.) Demonstration:

Computing Resources

Mao: Software + Home Directories

Minke01: WindowsXP+Linux (Chang)

Cowles-T5500: Windows7+Linux (Ara)

Cowles01: WindowsXP + Linux (Eric)

Zuse (will arrive in three weeks): Linux GPU Machine (Lab)

Oceania: /usr/local/bin

Hydra Computing Cluster

See: http://www.smast.umassd.edu/CMLAB/notebook/?page_id=142

Page 5: CMLAB Kickoff Meeting- Fall ‘10 1.) Weekly reporting 2.) Lab Meeting 3.) Computers and Accounts 4.) Backup policies 5.) Electronic lab notebook 6.) Demonstration:

BackupsAll systems are partially protected by using RAID5

Exception 1: Minke01 has no protectionException 2: Cowles-T5500 has no protection for Windows partition

I would like to establish a uniform backup policy. At this point I am thinking of:

1.) Backing up windows files to USB external drive2.) Backing up files on linux partition to Zuse using. User must choose what to backup to stay within allocated space.

Page 6: CMLAB Kickoff Meeting- Fall ‘10 1.) Weekly reporting 2.) Lab Meeting 3.) Computers and Accounts 4.) Backup policies 5.) Electronic lab notebook 6.) Demonstration:

Electronic Lab NotebookI have installed a WordPress blog on my website.

1.) Posts – dynamic entries that are displayed in reverse-chronological order on the Home page. Think of these as blog entries. They are useful for snippets of information that is dynamic, such as a HowTo.2.) Pages – these are like the more traditional form of entry on a website and are useful for displaying static information. Note I have already setup pages for each of your research projects as a well as a page for lab resources.

Username: Your SMAST account usernamePassword: abc123

Main Page: http://www.smast.umassd.edu/CMLAB/notebook/

Note the notebook contains two types of entries:

Use the notebook to help archive things that are useful for common knowledge such as how to use a piece of software or information on some new piece of software or a useful website you found for some data.

Page 7: CMLAB Kickoff Meeting- Fall ‘10 1.) Weekly reporting 2.) Lab Meeting 3.) Computers and Accounts 4.) Backup policies 5.) Electronic lab notebook 6.) Demonstration:

FVCOM Demo1.) Obtaining software from CVS2.) Building software3.) Choosing packages and setting compiler options4.) Compilation5.) Hydrodynamic Example: idealized estuary