| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| for_members [2019/01/14 19:52] – admin | for_members [2019/02/15 13:45] – [General guidelines for conducting research in Oncinfo lab] admin |
|---|
| ==== General guidelines for conducting research in Oncinfo lab ==== | ==== General guidelines for conducting research in the Oncinfo Lab ==== |
| |
| - All google docs that need to be edited by lab members should be put in Oncinfo [[https://drive.google.com/?tab=mo&authuser=0#folders/0B5Cpru0UXP0adTZTckg3aEd4SEE|folder]]. They should be kept confidential. Send your gmail address to Habil to get access to this folder. Then, create a subfolder with your name there, and create a google doc in your subfolder. Copy all items from this "For members" page to that google doc, and write "**Done**", "**Todo**", "**Skip**" in front of each item. | - All google docs that need to be edited by lab members should be put in Oncinfo [[https://drive.google.com/?tab=mo&authuser=0#folders/0B5Cpru0UXP0adTZTckg3aEd4SEE|folder]]. They should be kept confidential. Send your gmail address to Habil to get access to this folder. Remind him to add you his Oncinfo Google group. Then, create a subfolder with your name there, and create a google doc in your subfolder. Copy all items from this "For members" page to that google doc, and write "**Done**", "**Todo**", "**Skip**" in front of each item. |
| - Pass the online training courses required by the University e.g., conflict of interest, safety, etc. | - Pass the online training courses required by the University e.g., conflict of interest, safety, etc. |
| - All experiments and analysis are done on Unix. That is a __real__ Unix system like Linux, OS X, etc., NOT a virtual machine. Start with a [[http://www.ee.surrey.ac.uk/Teaching/Unix/|tutorial]] for beginners or the [[http://nebc.nerc.ac.uk/downloads/courses/Bio-Linux/bl8_latest.pdf|introduction]] to Bio-Linux. | - All experiments and analysis are done on Unix. That is a __real__ Unix system like Linux, OS X, etc., NOT a virtual machine. Start with a [[http://www.ee.surrey.ac.uk/Teaching/Unix/|tutorial]] for beginners or the [[http://nebc.nerc.ac.uk/downloads/courses/Bio-Linux/bl8_latest.pdf|introduction]] to Bio-Linux. |
| - Any file or data on this wiki that has restricted permissions, such as some paper pdfs or drafts, should not be shared with nonmembers unless authorized by the PI. | - Any file or data on this wiki that has restricted permissions, such as some paper pdfs or drafts, should not be shared with nonmembers unless authorized by the PI. |
| - All members should read and follow [[http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1000424|Bill's]] guidelines, and organize their files and folders accordingly and to some extend. Start by making a "~/proj" directory in your home folder that will eventually contain a subfolder for each project you are working on. Major subfolders must have a readme file for example to describe where the data is coming from. Your code folder must include a runall.R script that sources other scripts. Avoid sourcing scripts in other scripts except for the runall because then following and debugging the pipeline would be difficult. | - All members should read and follow [[http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1000424|Bill's]] guidelines, and organize their files and folders accordingly and to some extend. Start by making a "~/proj" directory in your home folder that will eventually contain a subfolder for each project you are working on. Major subfolders must have a readme file for example to describe where the data is coming from. Your code folder must include a runall.R script that sources other scripts. Avoid sourcing scripts in other scripts except for the runall because then following and debugging the pipeline would be difficult. |
| - Your code and documents should be stored in a Bitbucket repository like [[https://bitbucket.org/habilzare/genetwork|https://bitbucket.org/habilzare/genetwork]]. Sign up for an [[https://bitbucket.org/account/signup/|account]] and add your photo. Only then, send your username to Habil. If you are new to Bitbucket, take [[https://guides.co/g/bitbucket-101/11146|Bitbucket 101]]. You can [[https://confluence.atlassian.com/bitbucket/use-the-ssh-protocol-with-bitbucket-cloud-221449711.html|avoid]] having to manually type a password each time you pull using ssh. To add a key, click on your photo at the top right corner of Bitbucket page, Bitbucket settings, SSH keys, Add key. This trick is not appropriate for TACC clusters because we should not change our .ssh folder there. On the cluster, use https to clone instead of ssh. Do NOT skip this step. Before changing anything in a repository, read and abide to the conventions described in the main readme file. | - Your code and documents should be stored in a Bitbucket repository like [[https://bitbucket.org/habilzare/genetwork|https://bitbucket.org/habilzare/genetwork]]. Sign up for an [[https://bitbucket.org/account/signup/|account]] and add your photo. Do NOT sign in using your Google account. Only then, send your username to Habil. If you are new to Bitbucket, take [[https://guides.co/g/bitbucket-101/11146|Bitbucket 101]]. You can [[https://confluence.atlassian.com/bitbucket/use-the-ssh-protocol-with-bitbucket-cloud-221449711.html|avoid]] having to manually type a password each time you pull using ssh. To add a key, click on your photo at the top right corner of Bitbucket page, Bitbucket settings, SSH keys, Add key. This trick is not appropriate for TACC clusters because we should not change our .ssh folder there. On the cluster, use https to clone instead of ssh. Do NOT skip this step. Before changing anything in a repository, read and abide to the conventions described in the main readme file. |
| - Do NOT use space in the file or folder names. Do NOT include binary files such as png, pdf, RData, etc. in a Bitbucket repository unless on an exceptional basis. Instead, use e.g., ''rsync -avz -e ssh <usrname>@ls5.tacc.utexas.edu'' or ''scp ''to transfer files, and document the exact paths in a readme file in the corresponding folder. | - Do NOT use space in the file or folder names. Do NOT include binary files such as png, pdf, RData, etc. in a Bitbucket repository unless on an exceptional basis. Instead, use e.g., ''rsync -avz -e ssh <usrname>@ls5.tacc.utexas.edu'' or ''scp ''to transfer files, and document the exact paths in a readme file in the corresponding folder. |
| - If you want to use TACC resources, you first [[https://portal.tacc.utexas.edu/account-request|create]] an account, and then ask Habil to add you to a project. A simple test for running a job on Stampede cluster is the following. Look at their user [[https://portal.tacc.utexas.edu/user-guides/stampede|guide]] or [[https://srcc.stanford.edu/sge-slurm-conversion|this]] table of commands for more details. \\ $ ssh <username>@stampede.tacc.utexas.edu \\ $ cd ~zare \\ login4.stampede(1)$ sbatch -p normal -n 1 -t 3 ./test.sh \\ We usually use Lonestar5 for computing and Ranch for storage of large data. | - If you want to use TACC resources, you first [[https://portal.tacc.utexas.edu/account-request|create]] an account, and then ask Habil to add you to a project. A simple test for running a job on Stampede cluster is the following. Look at their user [[https://portal.tacc.utexas.edu/user-guides/stampede|guide]] or [[https://srcc.stanford.edu/sge-slurm-conversion|this]] table of commands for more details. \\ $ ssh <username>@stampede.tacc.utexas.edu \\ $ cd ~zare \\ login4.stampede(1)$ sbatch -p normal -n 1 -t 3 ./test.sh \\ We usually use Lonestar5 for computing and Ranch for storage of large data. |
| - If you are unfamiliar with prior, posterior, and likelihood, read about [[http://%5Bhttp://en.wikipedia.org/wiki/Bayesian_inference|Bayesian inference]]. | - If you are unfamiliar with prior, posterior, and likelihood, read about [[http://%5Bhttp://en.wikipedia.org/wiki/Bayesian_inference|Bayesian inference]]. |
| - To use ref.bib bibliography in bibtex, do the following: \\ a) cd proj \\ b) git clone [[mailto:git@bitbucket.org:habilzare/refs.git|git@bitbucket.org:habilzare/refs.git]] \\ c) At the bottom of your LaTeX document, write: \\ \bibliography{\detokenize{~/proj/refs/refs}} \\ d) To add a new entry, find the appropriate format using "Google Scholar Button" (see above, click on the quotation mark at the to right, and then BibTeX at the bottom) copy the entry and see if it is already in the refs.bib file. If not, add it in "**its right location"** (i.e., key are alphabetically ordered) and push. Use the key with the \cite command in your LaTeX file. To compile, use pdflatex, bibtex (without .tex), and pdflatex *2. | - To use ref.bib bibliography in bibtex, do the following: \\ a) cd proj \\ b) git clone [[mailto:git@bitbucket.org:habilzare/refs.git|git@bitbucket.org:habilzare/refs.git]] \\ c) At the bottom of your LaTeX document, write: \\ \bibliography{\detokenize{~/proj/refs/refs}} \\ d) To add a new entry, find the appropriate format using "Google Scholar Button" (see above, click on the quotation mark at the to right, and then BibTeX at the bottom) copy the entry and see if it is already in the refs.bib file. If not, add it in "**its right location"** (i.e., key are alphabetically ordered) and push. Use the key with the \cite command in your LaTeX file. To compile, use pdflatex, bibtex (without .tex), and pdflatex *2. |
| - If you need to ssh into the lab machine you will need to have an account on the machine already. Then you will follow the following commands: ssh <user name>@10.102.163.212 | - Please cc Habil on any email that is related to scientific or logistic aspects of your research in the lab, your career development activities, and communications among lab members on issues related to the lab. When you send an email to multiple people, mention the primary addressee at the top. It helps drawing the attention of the addressee, and also shows your respect to others who do not need to read your whole message. Usually using "reply-to-all" is preferred on emails with multiple recipients. |
| - Usually, the latest version of Ubuntu is missing some dependencies for the R packages Pigengene, WGCNA, and GEOquery. To easily install these dependencies, download [[:file_view_ubuntuinstall.sh_614871151_ubuntuinstall.sh|this]] script, as well as [[:file_view_pigengeneubuntuinstall.r_614318347_pigengeneubuntuinstall.r|pigengeneUbuntuInstall.R]] to a local directory. Navigate to that directory and then run: \\ $ chmod +x ubuntuInstall.sh \\ $ ./ubuntuInstall.sh \\ $ Rscript pigengeneUbuntuInstall.R | |
| - Please cc Habil on any email that is related to scientific or logistic aspects of your research in the lab, your career development activities, and communications among lab members on issues related to the lab. When you send an email to multiple people, mention the primary addressee at the top. It helps drawing the attention of the addressee, and also shows your respect to others who do not need to read your whole message. | |
| - As employees of UT Health, we can get facilitated appointments with UT Health primary care physicians (call: 210-450-9090). | - As employees of UT Health, we can get facilitated appointments with UT Health primary care physicians (call: 210-450-9090). |
| - If you are considering ultimately getting jobs in computation biology or bioinformatics, have a look at postings at the [[http://bioinformatics.org|bioinformatics.org]] website __within the first week__ after joining the lab. For academic positions, see the Nature Jobs and Science Careers websites. Read the articles on "[[http://oncinfo.org/how_to|How to]] rescue US biomedical research from its systemic flaws?" if you are, or want to be, a PhD student. | - If you are considering ultimately getting jobs in computation biology or bioinformatics, have a look at postings at the [[http://bioinformatics.org|bioinformatics.org]] website __within the first week__ after joining the lab. For academic positions, see the Nature Jobs and Science Careers websites. Read the articles on "[[http://oncinfo.org/how_to|How to]] rescue US biomedical research from its systemic flaws?" if you are, or want to be, a PhD student. |
| | |
| |
| ==== Some references ==== | ==== Some references ==== |
