✎ for_members [oncinfo]

You've loaded an old revision of the document! If you save it, you will create a new version with this data.

<h3>How can I join the Oncinfo Lab?</h3>
<div class="level3">

To join and be a good member of the Oncinfo Lab, you need to:

<ol>
<li class="level1"> Be organized and disciplined, otherwise your efforts will be fruitless and lost even if you make important discoveries. Other lab members will enjoy working with you if your code is clean and you can clearly talk about your project.</li>
<li class="level1"> Know how to write programs and have some knowledge of biology.</li>
<li class="level1"> Be passionate about science, otherwise a good programmer should easily find other jobs with a multiple-fold salary.</li>
<li class="level1"> Work hard, otherwise even a genius will not get to anywhere if they do not move.</li>
<li class="level1"> Be talented. Nobody knows everything that is needed to do multidisciplinary research. You should be able to learn many things that you were not taught in courses. You often need to find novel solutions for small and big challenges that you face because you are the first person who is working on your specific study.</li>
<li class="level1"> Be knowledgeable because we are not interested in reinventing the wheel. 
The above items are ordered based on importance. The most critical one is discipline.</li>
</ol>

</div>

<h3>General guidelines for conducting research in the Oncinfo Lab</h3>
<div class="level3">
<ol>
<li class="level1"> All Google docs that need to be edited by lab members should be put in Oncinfo <a href="https://drive.google.com/?tab=mo&authuser=0#folders/0B5Cpru0UXP0adTZTckg3aEd4SEE" class="urlextern" title="https://drive.google.com/?tab=mo&authuser=0#folders/0B5Cpru0UXP0adTZTckg3aEd4SEE" rel="ugc nofollow">folder</a>. They should be kept confidential. Send your gmail address to Habil to get access to this folder. Remind him to add you to his Oncinfo Google 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 (<a href="https://docs.google.com/document/d/1o8s5_S-Lx-xXl1MVHV6MN7-bZrjitoKctm9CxRAdXu4/edit#heading=h.2l9mzouq3lij" class="urlextern" title="https://docs.google.com/document/d/1o8s5_S-Lx-xXl1MVHV6MN7-bZrjitoKctm9CxRAdXu4/edit#heading=h.2l9mzouq3lij" rel="ugc nofollow">example</a>).</li>
<li class="level1"> If you have a lab computer, add the tag number written on the back of the laptop, your name, and the date you start using it in the <a href="https://docs.google.com/spreadsheets/d/1A6ouCCPov5VXt7xBCdTh7Cwc6jtPJGGJlekmGnKL5JY/edit#gid=441648294" class="urlextern" title="https://docs.google.com/spreadsheets/d/1A6ouCCPov5VXt7xBCdTh7Cwc6jtPJGGJlekmGnKL5JY/edit#gid=441648294" rel="ugc nofollow">table</a> of computers. Your drive must be always encrypted. E.g., on macOS, you can make sure FileValut is on like <a href="/lib/exe/fetch.php?media=screen_shot_2020-02-15_at_10.24.09_pm.png" class="media mediafile mf_png" title="screen_shot_2020-02-15_at_10.24.09_pm.png (295.9 KB)">this</a>. Take a similar screenshot that shows your name at the upper right corner, and post it on your lab notebook. Mackbooks sometimes use their storage as RAM, so leave at least 50-100 GB empty all the time.</li>
<li class="level1"> Pass the online training courses required by the University e.g., conflict of interest, safety, etc.</li>
<li class="level1"> Ask for help <a href="https://codingkilledthecat.wordpress.com/2012/06/26/how-to-ask-for-programming-help/" class="urlextern" title="https://codingkilledthecat.wordpress.com/2012/06/26/how-to-ask-for-programming-help/" rel="ugc nofollow">professionally</a>, e.g., include the exact text of the error message.</li>
<li class="level1"> 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 <a href="https://web.archive.org/web/20230815043906/http://www.ee.surrey.ac.uk/Teaching/Unix/" class="urlextern" title="https://web.archive.org/web/20230815043906/http://www.ee.surrey.ac.uk/Teaching/Unix/" rel="ugc nofollow">tutorial</a> for beginners.</li>
<li class="level1"> <a href="http://www.r-project.org/" class="urlextern" title="http://www.r-project.org/" rel="ugc nofollow">R</a> is primarily used for statistical analysis and other scripting purposes in Oncinfo Lab. <a href="https://www.coursera.org/course/rprog" class="urlextern" title="https://www.coursera.org/course/rprog" rel="ugc nofollow">This</a> is a good online course on R which takes about 1 month to complete. A couple of days should be enough to read the <a href="http://cran.r-project.org/doc/manuals/R-intro.pdf" class="urlextern" title="http://cran.r-project.org/doc/manuals/R-intro.pdf" rel="ugc nofollow">CRAN's</a> good guide for starters to get the basic ideas, cover the <a href="http://www.r-tutor.com/r-introduction" class="urlextern" title="http://www.r-tutor.com/r-introduction" rel="ugc nofollow">introduction</a> section from R-Tutorial, or learn R preliminaries <a href="https://rpubs.com/alinemati/learning_R_step_by_step" class="urlextern" title="https://rpubs.com/alinemati/learning_R_step_by_step" rel="ugc nofollow">step by step</a> when you have a goog <a href="https://cran.r-project.org/doc/contrib/Short-refcard.pdf" class="urlextern" title="https://cran.r-project.org/doc/contrib/Short-refcard.pdf" rel="ugc nofollow">cheat</a> sheet. Avoid using explicit <a href="https://www.datacamp.com/community/tutorials/tutorial-on-loops-in-r" class="urlextern" title="https://www.datacamp.com/community/tutorials/tutorial-on-loops-in-r" rel="ugc nofollow">loops</a> and <code>apply()</code> in R when possible. <a href="https://www.datacamp.com/" class="urlextern" title="https://www.datacamp.com/" rel="ugc nofollow">DataCamp</a> facilitates reading about R and running examples at the same time using a browser. Those who know R to some extent can use these books: Computational <a href="https://compgenomr.github.io/book/" class="urlextern" title="https://compgenomr.github.io/book/" rel="ugc nofollow">Genomics</a> with R, Bioinformatics with R <a href="/lib/exe/fetch.php?media=bioinformatics-r-cookbook.pdf" class="media mediafile mf_pdf" title="bioinformatics-r-cookbook.pdf (12.2 MB)">Cookbook</a>, <a href="http://adv-r.had.co.nz/" class="urlextern" title="http://adv-r.had.co.nz/" rel="ugc nofollow">Advanced</a> R (<a href="https://adv-r.hadley.nz/" class="urlextern" title="https://adv-r.hadley.nz/" rel="ugc nofollow">2nd</a> Edition) by Hadley Wickham, <a href="https://booksoncode.com/articles/best-r-books-for-beginners" class="urlextern" title="https://booksoncode.com/articles/best-r-books-for-beginners" rel="ugc nofollow">etc</a>. to gradually learn more as they proceed in a project. The next step after learning R is to learn <a href="http://www.nature.com/nmeth/journal/v12/n2/full/nmeth.3252.html" class="urlextern" title="http://www.nature.com/nmeth/journal/v12/n2/full/nmeth.3252.html" rel="ugc nofollow">Bioconductor</a>. You can install most packages that we use in the lab by: 
<code>source("~/proj/alzheimer/code/utilities/makeOncinfoUt.R"); 
 OncinfoUt::call.libraries()</code></li>
<li class="level1"> Using <a href="https://en.wikipedia.org/wiki/Emacs" class="urlextern" title="https://en.wikipedia.org/wiki/Emacs" rel="ugc nofollow">Emacs</a>as a powerful, general purpose, text editor is <a href="https://robertamezquita.github.io/post/2017-04-07-my-emacs-setup/" class="urlextern" title="https://robertamezquita.github.io/post/2017-04-07-my-emacs-setup/" rel="ugc nofollow">encouraged</a> (<a href="http://www2.lib.uchicago.edu/keith/tcl-course/emacs-tutorial.html" class="urlextern" title="http://www2.lib.uchicago.edu/keith/tcl-course/emacs-tutorial.html" rel="ugc nofollow">tutorial</a>). In terminal, you can start it by typing emacs even in an SSH session. On Ubuntu you can simply install Emacs using Software Center, or by Package Synaptics, or by the following command: <code>sudo apt-get install emacs</code>. On OS X, you can install <a href="https://emacsformacosx.com/" class="urlextern" title="https://emacsformacosx.com/" rel="ugc nofollow">Emacs</a> For MAC OS X, which is better than Aquamacs. A less recommended option is <a href="https://vigou3.gitlab.io/emacs-modified-macos/" class="urlextern" title="https://vigou3.gitlab.io/emacs-modified-macos/" rel="ugc nofollow">Emacs Modified for macOS</a>, which supports <a href="https://ess.r-project.org/" class="urlextern" title="https://ess.r-project.org/" rel="ugc nofollow">ESS</a> and <a href="https://www.gnu.org/software/auctex/" class="urlextern" title="https://www.gnu.org/software/auctex/" rel="ugc nofollow">AUCTeX</a>. You can customize your emacs by editing .emacs file. Feel free to copy some, but not all, commands from Habil's .emacs file for <a href="https://www.dropbox.com/s/pdt6fbho57k421d/emacs_UTosx2018" class="urlextern" title="https://www.dropbox.com/s/pdt6fbho57k421d/emacs_UTosx2018" rel="ugc nofollow">macOS</a>. You can add these commands and automatically install the following packages by installing <a href="https://www.dropbox.com/s/d21azt9hg65sv3f/oncinfo.el?dl=0" class="urlextern" title="https://www.dropbox.com/s/d21azt9hg65sv3f/oncinfo.el?dl=0" rel="ugc nofollow">oncinfo.el</a> Emacs package, which is not tested well yet. As of 2019, Habil's favorite packages include: rainbow-delimiters, idle-highlight-in-visible-buffers-mode, auto-highlight-symbol, auto-complete-auctex, auto-complete, ess, and yaml. For guidelines on installing these packages and other emacs customizations, see the notes on <a href="/doku.php?id=how_to" class="wikilink1" title="how_to" data-wiki-id="how_to">How to</a> page.</li>
<li class="level1"> Using proprietary file formats is not professional when you are sharing information (e.g., your CV) with others. The pdf and png formats are OK and portable. Use Google Docs instead of .docx (<a href="http://You can use this sample as a template: https://docs.google.com/presentation/d/18kjTNomXuH0UUfL5KZYA1qjb3Zck39E8rnyZ-olocZQ/edit#slide=id.g6f6cf82c93_0_99" class="urlextern" title="http://You can use this sample as a template: https://docs.google.com/presentation/d/18kjTNomXuH0UUfL5KZYA1qjb3Zck39E8rnyZ-olocZQ/edit#slide=id.g6f6cf82c93_0_99" rel="ugc nofollow">sample</a>), Google Presentation instead of .ppt, .zip or tar.gz instead of rar, etc. See this <a href="https://free-for.dev/" class="urlextern" title="https://free-for.dev/" rel="ugc nofollow">list</a> of free tiers for developers.</li>
<li class="level1"> <a href="https://www.youtube.com/watch?v=WsofH466lqk" class="urlextern" title="https://www.youtube.com/watch?v=WsofH466lqk" rel="ugc nofollow">This</a> video illustrates transcription (<a href="https://en.wikipedia.org/wiki/Transcription_(genetics)" class="urlextern" title="https://en.wikipedia.org/wiki/Transcription_(genetics)" rel="ugc nofollow">wikipedia</a>, <a href="https://www.youtube.com/watch?v=5MfSYnItYvg" class="urlextern" title="https://www.youtube.com/watch?v=5MfSYnItYvg" rel="ugc nofollow">video 2</a>), more videos on <a href="https://www.youtube.com/watch?v=OEWOZS_JTgk" class="urlextern" title="https://www.youtube.com/watch?v=OEWOZS_JTgk" rel="ugc nofollow">gene expression</a> (<a href="https://en.wikipedia.org/wiki/Gene_expression" class="urlextern" title="https://en.wikipedia.org/wiki/Gene_expression" rel="ugc nofollow">wikipedia</a>), <a href="https://www.youtube.com/watch?v=TfYf_rPWUdY" class="urlextern" title="https://www.youtube.com/watch?v=TfYf_rPWUdY" rel="ugc nofollow">translation</a> (<a href="https://www.youtube.com/watch?v=5bLEDd-PSTQ" class="urlextern" title="https://www.youtube.com/watch?v=5bLEDd-PSTQ" rel="ugc nofollow">detailed</a>), etc.</li>
<li class="level1"> All members should know about central <a href="https://en.wikipedia.org/wiki/Central_dogma_of_molecular_biology" class="urlextern" title="https://en.wikipedia.org/wiki/Central_dogma_of_molecular_biology" rel="ugc nofollow">dogma</a> of biology, which is almost enough biological knowledge to start the majority of projects. Familiarity with some basic concepts such as <a href="https://en.wikipedia.org/wiki/Exon" class="urlextern" title="https://en.wikipedia.org/wiki/Exon" rel="ugc nofollow">exon</a>, intron, <a href="https://www.youtube.com/watch?v=CZeN-IgjYCo" class="urlextern" title="https://www.youtube.com/watch?v=CZeN-IgjYCo" rel="ugc nofollow">sequencing</a>, etc. is helpful. Watch <a href="https://www.dnalc.org/resources/3d/" class="urlextern" title="https://www.dnalc.org/resources/3d/" rel="ugc nofollow">animations</a> from DNA Learning Center.</li>
<li class="level1"> Any file or data on this wiki that has restricted permissions, such as some paper pdfs or drafts, should be kept confidential, and NOT be shared with nonmembers unless authorized by the PI.</li>
<li class="level1"> For future reference, please add the link to your presentations and manuscript drafts on the <a href="https://oncinfo.org/drafts" class="urlextern" title="https://oncinfo.org/drafts" rel="ugc nofollow">drafts</a>page. At a minimum, please include: the author, the date, the audience or collaborator, and the subject. Include the corresponding pipeline and experiment name in your presentation for future reference.</li>
<li class="level1"> All members should read and follow <a href="http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1000424" class="urlextern" title="http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1000424" rel="ugc nofollow">Bill's</a> guidelines, and organize their files and folders accordingly and to some extent. 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. Abide to the "<a href="https://bitbucket.org/habilzare/template/src/master/" class="urlextern" title="https://bitbucket.org/habilzare/template/src/master/" rel="ugc nofollow">Rules</a> for developing pipelines". In particular, your code folder must include a runall.R script that sources other scripts. Avoid sourcing scripts in other scripts except for the runall, functions, and libraries because then following and debugging the pipeline would be difficult. At the top of each individual script, please brielfy explain what it does, and sign it by writing &lt;your name>, &lt;YYYY-MM-DD>.</li>
<li class="level1"> Your code and documents should be stored in a Bitbucket repository like <a href="https://bitbucket.org/habilzare/alzheimer/src/master/" class="urlextern" title="https://bitbucket.org/habilzare/alzheimer/src/master/" rel="ugc nofollow">https://bitbucket.org/habilzare/alzheimer/src/master/</a>. Sign up for an <a href="https://bitbucket.org/account/signup/" class="urlextern" title="https://bitbucket.org/account/signup/" rel="ugc nofollow">account</a> and add your photo. Do <a href="/lib/exe/fetch.php?media=wiki:public:bitbucket_account.png" class="media mediafile mf_png" title="wiki:public:bitbucket_account.png (212.1 KB)">NOT</a> sign in using your Google account. Only then, send your username and the corresponding email to Habil. If you are new to Bitbucket, spend an hour on the <a href="https://confluence.atlassian.com/bitbucket/tutorial-learn-bitbucket-with-git-759857287.html" class="urlextern" title="https://confluence.atlassian.com/bitbucket/tutorial-learn-bitbucket-with-git-759857287.html" rel="ugc nofollow">tutorial</a>. Taking <a href="https://guides.co/g/bitbucket-101/11146" class="urlextern" title="https://guides.co/g/bitbucket-101/11146" rel="ugc nofollow">Bitbucket 101</a> is NOT needed for beginners. You can <a href="https://confluence.atlassian.com/bitbucket/use-the-ssh-protocol-with-bitbucket-cloud-221449711.html" class="urlextern" title="https://confluence.atlassian.com/bitbucket/use-the-ssh-protocol-with-bitbucket-cloud-221449711.html" rel="ugc nofollow">avoid</a> having to manually type a password each time you pull using ssh. To add a key, click on settings at the top right corner of Bitbucket page, SSH keys, Add key. Use ssh to clone a repository, NOT https. Do NOT mess up with other's git folders on the cluster. You should only clone, pull, and push in your own home or work directory. Do NOT skip this step. Before changing anything in a repository, read and abide to the conventions described in the main readme file.</li>
<li class="level1"> 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 <a href="https://explainshell.com/explain?cmd=rsync+-avz" class="urlextern" title="https://explainshell.com/explain?cmd=rsync+-avz" rel="ugc nofollow">e.g.,</a><code>rsync -avz -e ssh &lt;usrname>@ls6.tacc.utexas.edu</code> or <code>scp </code>to transfer files between the cluster and your computer, and document the exact paths in a readme file in the corresponding folder. Add the readme file to the repository.</li>
<li class="level1"> If you want to use TACC resources, you first <a href="https://portal.tacc.utexas.edu/account-request" class="urlextern" title="https://portal.tacc.utexas.edu/account-request" rel="ugc nofollow">create</a> an account, and then ask Habil to add you to a project. Source <code>/work/03270/zare/Install/oncinfo_settings</code> in your .bashrc or other bash scripts so that you do not need to install the software that we often need and are already installed by other lab members. We usually use Lonestar and Maverick for computing, and we archive large data on Ranch based on <a href="https://docs.google.com/document/d/17VkB7_HQUq7yeSr906Qlh7q8TlFX5nvP5a1F9csXBGY/edit" class="urlextern" title="https://docs.google.com/document/d/17VkB7_HQUq7yeSr906Qlh7q8TlFX5nvP5a1F9csXBGY/edit" rel="ugc nofollow">this</a> protocol. A simple test for running a job on the Lonestar cluster is the following. Look at their user <a href="https://portal.tacc.utexas.edu/user-guides/lonestar5" class="urlextern" title="https://portal.tacc.utexas.edu/user-guides/lonestar5" rel="ugc nofollow">guide</a> and <a href="https://srcc.stanford.edu/sge-slurm-conversion" class="urlextern" title="https://srcc.stanford.edu/sge-slurm-conversion" rel="ugc nofollow">this</a> table of commands for more details. 
<code>$ ssh &lt;username>oIWIKIo@ls6.tacc.utexas.edu 
 $ cd ~zare 
 login1.ls6(1099)$ cat ./test.mpi</code> 
<code>login1.ls6(1099)$ sbatch ./test.mpi</code> 
You can monitor your jobs using <code>squeue -u &lt;usrname></code>. The output will be saved in the <code>~/temp</code> subfolder. If there are multiple files in this folder, look at the newest one. 
The above command will submit the job to the development queue. If you want to submit a job to the normal queue, you can do the following: 
<code>login1.ls6(1099)$ sbatch -p normal -n 1 -t 2 ./test.mpi</code> 
<a href="https://tacc-cloud.readthedocs.io/projects/agave/en/latest/index.htmlcIWIKIc" class="urlextern" title="https://tacc-cloud.readthedocs.io/projects/agave/en/latest/index.htmlcIWIKIc" rel="ugc nofollow">Tapis</a> is an advanced optional patform for submitting jobs from your local computer, not recommended for beginners. Before submitting many jobs, estimate the time and memory by submitting a single job or preferably, running your code on toy data. If you think running a complete job takes more than 10 minutes on the cluster, before submitting more similar jobs, let Habil check your code to make sure we do not miss any easy <a href="https://bitbucket.org/habilzare/alzheimer/commits/250cacf92ef6b2886973dc609c229032b42b2234" class="urlextern" title="https://bitbucket.org/habilzare/alzheimer/commits/250cacf92ef6b2886973dc609c229032b42b2234" rel="ugc nofollow">parallelization</a>. Familiarize yourself with <a href="https://docs.google.com/presentation/d/1TFjB16XmLk2Xo4qHJgGe1VfnIUonw9cIJmU1xCZxyL0/edit#slide=id.g242153ecf22_0_60" class="urlextern" title="https://docs.google.com/presentation/d/1TFjB16XmLk2Xo4qHJgGe1VfnIUonw9cIJmU1xCZxyL0/edit#slide=id.g242153ecf22_0_60" rel="ugc nofollow">Docker</a>, which you can use to test your code locally before runing it on the cluster. <a href="https://bitbucket.org/habilzare/genetwork/src/master/code/docker/readme.txt" class="urlextern" title="https://bitbucket.org/habilzare/genetwork/src/master/code/docker/readme.txt" rel="ugc nofollow">Use</a><code>habilzare/oncinfo:oncinfo-&lt;version></code> and modify only <code>habilzare/oncinfo:oncinfo-dev-&lt;version></code>.</li>
<li class="level1"> Every one should have a photo and their updated CV in pdf format on their personal page. <a href="/lib/exe/fetch.php?media=wiki:public:cv_template.zip" class="media mediafile mf_zip" title="wiki:public:cv_template.zip (215 KB)">This</a> is an optional LaTeX template. The permission of any lab notebook (lano) should be set to "hidden"and it is important that they be updated EVERY day. <a href="https://www.dokuwiki.org/dokuwiki" class="urlextern" title="https://www.dokuwiki.org/dokuwiki" rel="ugc nofollow">DokuWiki</a> provides us with two edit modes: ckg and DW. Use the one that is more convenient for you. Write your posts in anti-chronological order so that the newest post comes at the top. For facilitating future reference, avoid sending data as attachments. Instead, upload files to your lano and link to them where needed.</li>
<li class="level1"> You can install Google Scholar <a href="https://chrome.google.com/webstore/detail/google-scholar-button/ldipcbpaocekfooobnbcddclnhejkcpn?hl=en" class="urlextern" title="https://chrome.google.com/webstore/detail/google-scholar-button/ldipcbpaocekfooobnbcddclnhejkcpn?hl=en" rel="ugc nofollow">Button</a>add-on for an easier way of searching Google Scholar. You select the paper title and then click on the little blue icon on the top right corner. For any paper which you want to cite on the lab wiki, find it on Google Scholar, click on "More>oIWIKIoCite" and copy the MLA format. Also, use <a href="https://gsuite.google.com/marketplace/app/paperpile/894076725911cIWIKIc" class="urlextern" title="https://gsuite.google.com/marketplace/app/paperpile/894076725911cIWIKIc" rel="ugc nofollow">Paperpile</a> for easy citation in Google doc, and Math <a href="https://gsuite.google.com/marketplace/app/math_equations/825973477142" class="urlextern" title="https://gsuite.google.com/marketplace/app/math_equations/825973477142" rel="ugc nofollow">Equations</a> for writing and manipulating equations on Google presentations.</li>
<li class="level1"> Create a Nature <a href="https://idp.nature.com/register/natureuser?redirect_uri=https://www.nature.com/my-account/alerts" class="urlextern" title="https://idp.nature.com/register/natureuser?redirect_uri=https://www.nature.com/my-account/alerts" rel="ugc nofollow">account</a> for yourself. To get a monthly list of published papers in Nature Methods, subscribe to the corresponding alert . This can help you get a sense of where the field is going. You can also create an <a href="https://scholar.google.com/intl/en/scholar/help.html#alerts" class="urlextern" title="https://scholar.google.com/intl/en/scholar/help.html#alerts" rel="ugc nofollow">alert</a> on the Google Scholar to get regular updates on what is being published on the specific topic of your study.</li>
<li class="level1"> Code style in Oncinfo lab: We follow Hadley Wickhams’s R Style <a href="http://adv-r.had.co.nz/Style.html" class="urlextern" title="http://adv-r.had.co.nz/Style.html" rel="ugc nofollow">Guide</a> unless another convention is mentioned below. The goal is to include as much code as possible on 1 page so that it is easier to skim while keeping the overall structure such as proper indentation. Use <a href="https://contributions.bioconductor.org/r-code.html?q=inde#indentation" class="urlextern" title="https://contributions.bioconductor.org/r-code.html?q=inde#indentation" rel="ugc nofollow">2 spaces</a> (not tabs) for indentation. Like writing English texts, organize each script in small paragraphs and avoid extra white lines. Give each paragraph a short title in a comment. 
 When writing R code, use "<code>x &lt;- 5</code>" for assigning a value to a variable. Do NOT use "<code>x = 5</code>" or "<code>x&lt;-5</code>". We use<a href="https://en.wikipedia.org/wiki/Camel_case" class="urlextern" title="https://en.wikipedia.org/wiki/Camel_case" rel="ugc nofollow">camelCase</a>in R, so do NOT use underscore, '_', and dot, '.', in variable or function names. E.g., instead of "<code>inverse_of</code>", use "<code>inverseOf</code>" as a variable name or function name so that you can select it by 1 click. Almost all functions must return a list so that extending them will be easy. Use "<code>##</code>" for comments NOT a single "<code>#</code>". Boolean flags and variable names start with and as <a href="https://en.wikipedia.org/wiki/Auxiliary_verb" class="urlextern" title="https://en.wikipedia.org/wiki/Auxiliary_verb" rel="ugc nofollow">auxiliary</a> verb like <code>do</code>, <code>is</code>, or <code>has</code>, e.g., <code>doPlot</code>, <code>isSingle</code>, <code>hasMeta</code>, etc. Write the name of the loaded object in a comment in front of <code>load()</code>. 
Avoid long lines of code. Most lines should be < 90 characters, and all lines must be &lt;100 characters . Thus, do NOT include space when using <code>=</code> in function calls. Good example: <code>average &lt;- mean(feet[ ,"real"]/12+inches, na.rm=TRUE) ## Spaces only around "&lt;-" and after ","</code>. The space in "<code>[ ,</code>" is OK, which refers to all rows. It is better to place a space before the parenthesis after "<code>if (</code>", "<code>for (</code>", and alike, but do NOT use space between a function name and <code>"("</code> e.g., write <code>plot(Data)</code>. Write the FULL name of arguments when calling a function and do NOT reply on their order, which may change in the future. 
When the line is long, it usually means you need to extract some of it and define a new variable right above that line. 
Data structures in R can be ordered from simple to complex as follows: number , vector, matrix, and list. Always use the simplest possible data structure, e.g., do not use a list when you can use a matrix and do not use a matrix with one column when you can use a named vector. The reson is that R has more tools for simpler data structures, e.g., <code>sum</code> and <code>paste</code> work on vectors, but not lists. To add or modify a new element to a list use double square brackets like <a href="/lib/exe/fetch.php?media=wiki:public:screen_shot_2021-05-25_at_9.00.51_pm.png" class="media mediafile mf_png" title="wiki:public:screen_shot_2021-05-25_at_9.00.51_pm.png (13.4 KB)">this</a> , not "<code>$</code>". You can use "<code>$</code>" to access elements of a list like <code>A1 &lt;- list1$matrixA</code> (with some <a href="https://oncinfo.org/mohsens_lab_notebook#section20240211" class="urlextern" title="https://oncinfo.org/mohsens_lab_notebook#section20240211" rel="ugc nofollow">caveates</a>), but NOT to access a column of a data frame. Do not use <a href="https://www.datacamp.com/tutorial/pipe-r-tutorial" class="urlextern" title="https://www.datacamp.com/tutorial/pipe-r-tutorial" rel="ugc nofollow">pipes</a> in R (i.e., <code>%>%</code> and <code>|></code>) due to its <a href="https://stackoverflow.com/questions/38880352/should-i-avoid-programming-packages-with-pipe-operators" class="urlextern" title="https://stackoverflow.com/questions/38880352/should-i-avoid-programming-packages-with-pipe-operators" rel="ugc nofollow">drawbacks</a> outlined by Hadley <a href="https://r4ds.had.co.nz/pipes.html#when-not-to-use-the-pipe" class="urlextern" title="https://r4ds.had.co.nz/pipes.html#when-not-to-use-the-pipe" rel="ugc nofollow">Wickham</a>.</li>
<li class="level1"> Never copy code, instead generalize your code and write functions. If you are copying more than a line of code, most likely you are doing something wrong and WETting your code. Follow the <a href="https://en.wikipedia.org/wiki/Don't_repeat_yourself" class="urlextern" title="https://en.wikipedia.org/wiki/Don't_repeat_yourself" rel="ugc nofollow">DRY</a> principle.</li>
<li class="level1"> In your code, avoid using one letter variables such as i or a because they are very hard to track in the editor. Instead use ind or i1. Also, your variable name must be different from built-in functions such as ls in R.</li>
<li class="level1"> When possible, give and use column and row names to the matrixes. Also, give and use names for vectors as well as lists.</li>
<li class="level1"> When sharing the results with biologists collaborator, make your xlsx tables fancy e.g., by using bold and slightly larger fonts in the first row and column and also freezing the first row and column.</li>
<li class="level1"> Do’s and don’ts when <a href="https://web.archive.org/web/20181123152529/https://sicb.org/students/Dos_and_Donts.pdf" class="urlextern" title="https://web.archive.org/web/20181123152529/https://sicb.org/students/Dos_and_Donts.pdf" rel="ugc nofollow">submitting</a> papers.</li>
<li class="level1"> Make sure that your home, work, and scratch directories on the cluster are at least readable to the group, and not readable to others. E.g., in your .bashrc, set umask 007 and do the following: 
<code>chmod -R g+rwX,o-rwx $HOME $WORK $SCRATCH 
chmod 600 ~/.ssh/id_rsa ## If you have this file, it MUST be private. 
chmod g-w ~ ## Home must NOT be writable by the group otherwise submiting jobs will not be allowed. 
chmod 700 ~/.ssh ## Nobody other than you is allowed to change the sensative .ssh folder. 
chmod 644 ~/.ssh/id_rsa.pub ~/.ssh/authorized_keys ~/.ssh/known_hosts </code> 
There might be some <a href="https://unix.stackexchange.com/questions/37164/ssh-and-home-directory-permissions" class="urlextern" title="https://unix.stackexchange.com/questions/37164/ssh-and-home-directory-permissions" rel="ugc nofollow">exceptions</a> like your private ssh key at <code>~/.ssh/id_rsa</code>, which must be readable only by you. On Ranch, adding umask in .bashrc. does not work. Instead, create or modify ~/.cshrc. You need to do the above modifications on ALL clusters you use including Lonestar and Ranch.</li>
<li class="level1"> If you are unfamiliar with prior, posterior, and likelihood, read about <a href="https://en.wikipedia.org/wiki/Bayesian_inference" class="urlextern" title="https://en.wikipedia.org/wiki/Bayesian_inference" rel="ugc nofollow">Bayesian inference</a>.</li>
<li class="level1"> To use ref.bib bibliography in bibtex, do the following: 
a) cd proj 
b) git clone <a href="mailto:mailto:git@bitbucket.org:habilzare/refs.git" class="mail" title="mailto:git@bitbucket.org:habilzare/refs.git">git@bitbucket.org:habilzare/refs.git</a> 
 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.</li>
<li class="level1"> 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 draw 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. When possible, reply to the previous email on a topic and avoid creating another thread unnecessarily, which will complicate future references. Emails should be receive some sort of reply within 24 hours even if it is short like "I'll work on it". Otherwise, you will start your next email with "Sorry for the delay".</li>
<li class="level1"> As employees of UT Health, we can get facilitated appointments with UT Health primary care physicians (call: 210-450-9090), or alternatively use <a href="https://mdlnext.mdlive.com/home?matchtype=e&network=g&device=c&keyword=mdlive&adposition=&gclid=CjwKCAjwy_aUBhACEiwA2IHHQAXl6Lx_FzhKPaDyjCY5ry2vMwXnnqn7lFwcN4qM_rlQdqf3Be7V1BoCw60QAvD_BwE" class="urlextern" title="https://mdlnext.mdlive.com/home?matchtype=e&network=g&device=c&keyword=mdlive&adposition=&gclid=CjwKCAjwy_aUBhACEiwA2IHHQAXl6Lx_FzhKPaDyjCY5ry2vMwXnnqn7lFwcN4qM_rlQdqf3Be7V1BoCw60QAvD_BwE" rel="ugc nofollow">MDLIVE</a> to be virtually visited by a physician.</li>
<li class="level1"> If you are considering ultimately getting jobs in computational biology or bioinformatics, have a look at postings at the <a href="http://bioinformatics.org" class="urlextern" title="http://bioinformatics.org" rel="ugc nofollow">bioinformatics.org</a> website within the first week after joining the lab. For academic positions, see the Nature Jobs, Science Careers, and <a href="https://docs.google.com/document/d/1tRVpO0eFzYfl0f95X_X8YvE9DeQVX3vYBkmw4smRJLU/edit#" class="urlextern" title="https://docs.google.com/document/d/1tRVpO0eFzYfl0f95X_X8YvE9DeQVX3vYBkmw4smRJLU/edit#" rel="ugc nofollow">other</a> websites. Read the articles on "<a href="http://oncinfo.org/how_to" class="urlextern" title="http://oncinfo.org/how_to" rel="ugc nofollow">How to</a> rescue US biomedical research from its systemic flaws?" if you are, or want to be, a PhD student.</li>
<li class="level1"> If you want to use ROSMAP data, please create a Synapse <a href="https://www.synapse.org/#!RegisterAccount:0" class="urlextern" title="https://www.synapse.org/#!RegisterAccount:0" rel="ugc nofollow">account</a>, add your information to <a href="/lib/exe/fetch.php?media=second-ad-knowledge-portal-controlled-access-duc-march2022-v7.3-signed.pdf" class="media mediafile mf_pdf" title="second-ad-knowledge-portal-controlled-access-duc-march2022-v7.3-signed.pdf (958.9 KB)">this</a> file, and upload it again to Oncinfo without changing the file name. Let Habil know so that he uploads it on the Synapse <a href="https://help.adknowledgeportal.org/apd/Data-Use-Certificates.2623373330.html" class="urlextern" title="https://help.adknowledgeportal.org/apd/Data-Use-Certificates.2623373330.html" rel="ugc nofollow">website</a>. Then, accept Terms of Use through this <a href="https://www.synapse.org/#!AccessRequirements:ID=syn2910256&TYPE=ENTITY" class="urlextern" title="https://www.synapse.org/#!AccessRequirements:ID=syn2910256&TYPE=ENTITY" rel="ugc nofollow">link</a>.</li>
</ol>

</div>

<h3>Some references</h3>
<div class="level3">
<ol>
<li class="level1"> Two machine learning bibles, which summarize important topics in the field up to 2005: Bishop (<a href="/lib/exe/fetch.php?media=bishop-pattern_recongnition_and_machine_learning-1.pdf" class="media mediafile mf_pdf" title="bishop-pattern_recongnition_and_machine_learning-1.pdf (4.7 MB)">1</a>,<a href="/lib/exe/fetch.php?media=bishop-pattern_recongnition_and_machine_learning-2.pdf" class="media mediafile mf_pdf" title="bishop-pattern_recongnition_and_machine_learning-2.pdf (4.1 MB)">2</a> ) and <a href="http://statweb.stanford.edu/~tibs/ElemStatLearn/download.html" class="urlextern" title="http://statweb.stanford.edu/~tibs/ElemStatLearn/download.html" rel="ugc nofollow">Hasite et al.</a>. Anwar's cheat <a href="https://medium.com/swlh/cheat-sheets-for-machine-learning-interview-topics-51c2bc2bab4f" class="urlextern" title="https://medium.com/swlh/cheat-sheets-for-machine-learning-interview-topics-51c2bc2bab4f" rel="ugc nofollow">sheets</a>. A <a href="https://docs.google.com/spreadsheets/d/1AK8lqS-ztMhh8YoOaQ7ScIZmabrQ5AFxAyXKwYWiT04/edit#gid=0" class="urlextern" title="https://docs.google.com/spreadsheets/d/1AK8lqS-ztMhh8YoOaQ7ScIZmabrQ5AFxAyXKwYWiT04/edit#gid=0" rel="ugc nofollow">list</a> of some of the best courses in ML.</li>
<li class="level1"> An old list of computational biology <a href="https://docs.google.com/document/d/1fxqgQgsxf6Xd-8p0DUTyOGkeWNI5REW4zk1FXTxi2_I/edit" class="urlextern" title="https://docs.google.com/document/d/1fxqgQgsxf6Xd-8p0DUTyOGkeWNI5REW4zk1FXTxi2_I/edit" rel="ugc nofollow">books</a>. If you would like to have a hard copy of any these books or other books useful to your training and research, even in areas like psychology and management, please let Habil know. Molecular Biology of the Cell, by <a href="https://www.amazon.com/Molecular-Biology-Sixth-Bruce-Alberts/dp/0815345240" class="urlextern" title="https://www.amazon.com/Molecular-Biology-Sixth-Bruce-Alberts/dp/0815345240" rel="ugc nofollow">Alberts</a> et al, is a good self-contained book starting from basic biology concepts like DNA and ending in describing complex pathways and mechanisms like immune system (<a href="/lib/exe/fetch.php?media=screen_shot_2021-03-29_at_1.05.18_pm.png" class="media mediafile mf_png" title="screen_shot_2021-03-29_at_1.05.18_pm.png (481.5 KB)">contents</a>, <a href="/lib/exe/fetch.php?media=molecular_biology_of_the_cell_6th_editio.pdf" class="media mediafile mf_pdf" title="molecular_biology_of_the_cell_6th_editio.pdf (70.6 MB)">pdf</a> ).</li>
<li class="level1"> <a href="https://www.biostars.org/" class="urlextern" title="https://www.biostars.org/" rel="ugc nofollow">Biostars</a> is a good forum, similar to Stack Overflow in structure, but focused on bioinformatics and Computational Biology.</li>
<li class="level1"> <a href="http://www.wikiwand.com/en/List_of_free_online_bioinformatics_courses" class="urlextern" title="http://www.wikiwand.com/en/List_of_free_online_bioinformatics_courses" rel="ugc nofollow">List</a> of free online bioinformatics courses and some interesting <a href="http://bioconductor.org/help/events/" class="urlextern" title="http://bioconductor.org/help/events/" rel="ugc nofollow">events</a> in Bioconductor.</li>
<li class="level1"> <a href="https://www.coursera.org/course/pgm" class="urlextern" title="https://www.coursera.org/course/pgm" rel="ugc nofollow">This</a> is a good online course on Probabilistic Graphical Models by Daphne Koller.</li>
<li class="level1"> Bayesian Reasoning and Machine Learning, a good introductory <a href="http://web4.cs.ucl.ac.uk/staff/D.Barber/textbook/250214.pdf" class="urlextern" title="http://web4.cs.ucl.ac.uk/staff/D.Barber/textbook/250214.pdf" rel="ugc nofollow">book</a> by David Barber.</li>
<li class="level1"> <a href="http://stephenturner.us/edu.html" class="urlextern" title="http://stephenturner.us/edu.html" rel="ugc nofollow">Lists 1</a> and <a href="https://www.r-bloggers.com/2013/04/list-of-bioinformatics-workshops-and-training-resources/" class="urlextern" title="https://www.r-bloggers.com/2013/04/list-of-bioinformatics-workshops-and-training-resources/" rel="ugc nofollow">2</a> of bioinformatics workshops.</li>
<li class="level1"> A 5-minutes introduction to next-generation sequencing <a href="https://www.youtube.com/watch?annotation_id=annotation_228575861&feature=iv&src_vid=womKfikWlxM&v=fCd6B5HRaZ8" class="urlextern" title="https://www.youtube.com/watch?annotation_id=annotation_228575861&feature=iv&src_vid=womKfikWlxM&v=fCd6B5HRaZ8" rel="ugc nofollow">video</a>.</li>
</ol>

</div>

<h3>Fun stuff</h3>
<div class="level3">
<ol>
<li class="level1"> Inner <a href="https://www.youtube.com/watch?v=yKW4F0Nu-UY" class="urlextern" title="https://www.youtube.com/watch?v=yKW4F0Nu-UY" rel="ugc nofollow">Life</a> Of A Cell.</li>
<li class="level1"> The Dark Age of the <a href="https://www.youtube.com/watch?v=iyc3bDFk84w&src_vid=uabNtlLfYyU&feature=iv&annotation_id=annotation_558059" class="urlextern" title="https://www.youtube.com/watch?v=iyc3bDFk84w&src_vid=uabNtlLfYyU&feature=iv&annotation_id=annotation_558059" rel="ugc nofollow">Universe</a>, a good visualization of the big bang</li>
<li class="level1"> <a href="https://www.theguardian.com/society/2015/nov/19/pigeons-can-identify-cancerous-tissue-on-x-rays-study-finds" class="urlextern" title="https://www.theguardian.com/society/2015/nov/19/pigeons-can-identify-cancerous-tissue-on-x-rays-study-finds" rel="ugc nofollow">Pigeons</a> can learn to diagnose breast cancer with <a href="http://journals.plos.org/plosone/article?id=10.1371/journal.pone.0141357" class="urlextern" title="http://journals.plos.org/plosone/article?id=10.1371/journal.pone.0141357" rel="ugc nofollow">99</a>% accuracy.</li>
<li class="level1"> <a href="https://www.youtube.com/watch?v=jAhjPd4uNFY" class="urlextern" title="https://www.youtube.com/watch?v=jAhjPd4uNFY" rel="ugc nofollow">CRISPR</a> is an evolutionary tool for editing DNA, which <a href="https://www.youtube.com/watch?v=1BXYSGepx7Q" class="urlextern" title="https://www.youtube.com/watch?v=1BXYSGepx7Q" rel="ugc nofollow">reduces</a> the time and cost of genome modification by an order of magnitude.</li>
</ol>

</div>

Editor Height px Turn supplementary image paste support on

Edit summary: Minor changes

oncinfo

Site Tools

User Tools

Site Tools

Page Tools

User Tools