<?xml version='1.0'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:atom="http://www.w3.org/2005/Atom" >
<channel>
	<title><![CDATA[BOL: Related items]]></title>
	<link>https://bioinformaticsonline.com/related/19272?offset=460</link>
	<atom:link href="https://bioinformaticsonline.com/related/19272?offset=460" rel="self" type="application/rss+xml" />
	<description><![CDATA[]]></description>
	
	<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/39884/retrieving-taxonomic-information-with-r</guid>
	<pubDate>Thu, 29 Aug 2019 01:38:39 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/39884/retrieving-taxonomic-information-with-r</link>
	<title><![CDATA[Retrieving Taxonomic Information with R]]></title>
	<description><![CDATA[<p>This vignette will introduce users to the retrieval of taxonomic information with&nbsp;<code>myTAI</code>. The&nbsp;<code>taxonomy()</code>&nbsp;function implemented in&nbsp;<code>myTAI</code>&nbsp;relies on the powerful package&nbsp;<a href="https://github.com/ropensci/taxize">taxize</a>. Nevertheless, taxonomic information retrieval has been customized for the&nbsp;<code>myTAI</code>&nbsp;standard and for organism specific information retrieval.</p>
<p>Specifically, the&nbsp;<code>taxonomy()</code>&nbsp;function implemented in&nbsp;<code>myTAI</code>&nbsp;can be used to classify genomes according to phylogenetic classification into Phylostrata (Phylostratigraphy) or to retrieve species specific taxonomic information when performing Divergence Stratigraphy (see&nbsp;<a href="https://cran.r-project.org/web/packages/myTAI/vignettes/Introduction.html">Introduction</a>&nbsp;for details).</p><p>Address of the bookmark: <a href="https://cran.r-project.org/web/packages/myTAI/vignettes/Taxonomy.html" rel="nofollow">https://cran.r-project.org/web/packages/myTAI/vignettes/Taxonomy.html</a></p>]]></description>
	<dc:creator>Rahul Nayak</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/40463/%E2%80%98dockr%E2%80%99-the-r-container</guid>
	<pubDate>Mon, 23 Dec 2019 09:56:49 -0600</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/40463/%E2%80%98dockr%E2%80%99-the-r-container</link>
	<title><![CDATA[‘dockr’: the R container]]></title>
	<description><![CDATA[<p><code>dockr</code> 0.8.6 is now available on CRAN. <code>dockr</code> is a minimal toolkit to build a lightweight Docker container image for your R package, in which the package itself is available. The Docker image seeks to mirror your R session as close as possible with respect to R specific dependencies. Both dependencies on CRAN R packages as well as local non-CRAN R packages will be included in the Docker container image.</p>
<p>If you want to know, how Docker works, and why you should consider using Docker, please take a look at the <a href="https://www.docker.com/why-docker" target="_blank">Docker website</a>.</p><p>Address of the bookmark: <a href="https://www.docker.com/why-docker" rel="nofollow">https://www.docker.com/why-docker</a></p>]]></description>
	<dc:creator>Jit</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/40964/panev-an-r-package-for-a-pathway-based-network-visualization</guid>
	<pubDate>Sun, 09 Feb 2020 12:41:52 -0600</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/40964/panev-an-r-package-for-a-pathway-based-network-visualization</link>
	<title><![CDATA[PANEV: an R package for a pathway-based network visualization]]></title>
	<description><![CDATA[<p><span>PANEV (PAthway NEtwork Visualizer) is an R package set for gene/pathway-based network visualization. Based on information available on KEGG, it visualizes genes within a network of multiple levels (from 1 to&nbsp;</span><em>n</em><span>) of interconnected upstream and downstream pathways. The network graph visualization helps to interpret functional profiles of a cluster of genes.</span></p>
<p><span><a href="https://bmcbioinformatics.biomedcentral.com/articles/10.1186/s12859-020-3371-7">https://bmcbioinformatics.biomedcentral.com/articles/10.1186/s12859-020-3371-7</a></span></p><p>Address of the bookmark: <a href="https://github.com/vpalombo/PANEV" rel="nofollow">https://github.com/vpalombo/PANEV</a></p>]]></description>
	<dc:creator>Jit</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/41272/rainbowr-reliable-association-inference-by-optimizing-weights-with-r-r-package-for-snp-set-gwas-and-multi-kernel-mixed-model</guid>
	<pubDate>Fri, 28 Feb 2020 23:27:37 -0600</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/41272/rainbowr-reliable-association-inference-by-optimizing-weights-with-r-r-package-for-snp-set-gwas-and-multi-kernel-mixed-model</link>
	<title><![CDATA[RAINBOWR: Reliable Association INference By Optimizing Weights with R (R package for SNP-set GWAS and multi-kernel mixed model)]]></title>
	<description><![CDATA[<p><code>RAINBOWR</code>(Reliable Association INference By Optimizing Weights with R) is a package to perform several types of <code>GWAS</code> as follows.</p>
<ul>
<li>Single-SNP GWAS with <code>RGWAS.normal</code> function</li>
<li>SNP-set (or gene set) GWAS with <code>RGWAS.multisnp</code> function (which tests multiple SNPs at the same time)</li>
<li>Check epistatic (SNP-set x SNP-set interaction) effects with <code>RGWAS.epistasis</code> (very slow and less reliable)</li>
</ul>
<p>https://github.com/KosukeHamazaki/RAINBOWR</p>
<p>https://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1007663</p>
<p>https://cran.r-project.org/web/packages/RAINBOWR/index.html</p><p>Address of the bookmark: <a href="https://github.com/KosukeHamazaki/RAINBOWR" rel="nofollow">https://github.com/KosukeHamazaki/RAINBOWR</a></p>]]></description>
	<dc:creator>Surabhi Chaudhary</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/42299/platypus-%E2%80%93-r-package-for-object-detection-and-image-segmentation</guid>
	<pubDate>Mon, 09 Nov 2020 02:56:25 -0600</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/42299/platypus-%E2%80%93-r-package-for-object-detection-and-image-segmentation</link>
	<title><![CDATA[Platypus – R package for object detection and image segmentation.]]></title>
	<description><![CDATA[<p><a href="https://github.com/maju116/platypus" target="_blank">platypus</a>&nbsp;is an R package for object detection and semantic segmentation. Currently using&nbsp;</p>
<div>platypus&nbsp;you can perform:</div>
<ul>
<li>multi-class semantic segmentation using&nbsp;U-Net&nbsp;architecture</li>
<li>multi-class object detection using&nbsp;YOLOv3&nbsp;architecture</li>
</ul>
<p>You can install the latest version of&nbsp;platypus&nbsp;with&nbsp;remotes&nbsp;package:</p>
<div>
<div>
<div>
<div>remotes::install_github("maju116/platypus")</div>
</div>
</div>
</div>
<p>Note that in order to install&nbsp;platypus&nbsp;you need to install&nbsp;keras&nbsp;and&nbsp;tensorflow&nbsp;packages and&nbsp;Tensorflow&nbsp;version&nbsp;&gt;= 2.0.0&nbsp;(&nbsp;Tensorflow 1.x&nbsp;will not be supported!)</p><p>Address of the bookmark: <a href="https://github.com/maju116/platypus" rel="nofollow">https://github.com/maju116/platypus</a></p>]]></description>
	<dc:creator>BioStar</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/43848/r-shiny-in-life-sciences-%E2%80%93-top-7-dashboard-examples</guid>
	<pubDate>Fri, 01 Apr 2022 19:05:03 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/43848/r-shiny-in-life-sciences-%E2%80%93-top-7-dashboard-examples</link>
	<title><![CDATA[R Shiny in Life Sciences – Top 7 Dashboard Examples]]></title>
	<description><![CDATA[<p><span>&nbsp;R Shiny is one of the easiest ways for developers to make production-ready dashboards when speed and functionality are crucial. Shiny is approachable with a lot of documentation available, and because of this, a lot of developers/researchers with non-coding backgrounds are able to produce some impressive results. The whole ecosystem is easy to get your head around and pretty much limitless with regard to what you can do.</span></p><p>Address of the bookmark: <a href="https://www.r-bloggers.com/2022/03/r-shiny-in-life-sciences-top-7-dashboard-examples/" rel="nofollow">https://www.r-bloggers.com/2022/03/r-shiny-in-life-sciences-top-7-dashboard-examples/</a></p>]]></description>
	<dc:creator>Neel</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/44487/r-package-for-pca-analysis</guid>
	<pubDate>Sun, 24 Mar 2024 20:06:24 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/44487/r-package-for-pca-analysis</link>
	<title><![CDATA[R Package for PCA Analysis]]></title>
	<description><![CDATA[<p><span>An R package for performing principal component analysis (PCA) of genomics data. The package performs PCA, generates the publication-ready plots, and identifies population-specific outlier individuals. The package can be accessed on GitHub:&nbsp;https://github.com/Devashish13/PopulationStructure</span></p><p>Address of the bookmark: <a href="https://rpubs.com/Devashish13/PCAGenomics" rel="nofollow">https://rpubs.com/Devashish13/PCAGenomics</a></p>]]></description>
	<dc:creator>LEGE</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/pages/view/30654/source-code-and-pseudo-code</guid>
	<pubDate>Mon, 23 Jan 2017 10:17:35 -0600</pubDate>
	<link>https://bioinformaticsonline.com/pages/view/30654/source-code-and-pseudo-code</link>
	<title><![CDATA[Source Code and Pseudo Code !!]]></title>
	<description><![CDATA[<p>An <span style="text-decoration: underline;">algorithm</span> is a procedure for solving a problem in terms of the actions to be executed and the order in which those actions are to be executed. An algorithm is merely the sequence of steps taken to solve a problem. The steps are normally "sequence," "selection, " "iteration," and a case-type statement.</p><p>In C, "sequence statements" are imperatives. The "selection" is the "if then else" statement, and the iteration is satisfied by a number of statements, such as the "while," " do," and the "for," while the case-type statement is satisfied by the "switch" statement.</p><hr><p><span style="text-decoration: underline;">Pseudocode</span> is an artificial and informal language that helps programmers develop algorithms. Pseudocode is a "text-based" detail (algorithmic) design tool.</p><p>The rules of Pseudocode are reasonably straightforward. All statements showing "dependency" are to be indented. These include while, do, for, if, switch. Examples below will illustrate this notion.</p><p><strong> GUIDE TO PSEUDOCODE LEVEL OF DETAIL: Given record/file descriptions, pseudocode should be created in sufficient detail so as to directly support the programming effort. It is the purpose of pseudocode to elaborate on the algorithmic detail and not just cite an abstraction. </strong></p><hr><p>Examples:</p><p>1.</p><pre>If student's grade is greater than or equal to 60
    Print "passed"
else
    Print "failed"  
endif
</pre><hr><p>2.</p><pre>  
Set total to zero
Set grade counter to one
While grade counter is less than or equal to ten
    Input the next grade
    Add the grade into the total
endwhile 
Set the class average to the total divided by ten
Print the class average.
</pre><hr><p>3.</p><pre>Initialize total to zero
Initialize counter to zero
Input the first grade
while the user has not as yet entered the sentinel
   add this grade into the running total 
   add one to the grade counter  
   input the next grade (possibly the sentinel)
endwhile

if the counter is not equal to zero
   set the average to the total divided by the counter
   print the average  
else
   print 'no grades were entered' 
endif 
</pre><hr><p>4.</p><pre>initialize passes to zero
initialize failures to zero
initialize student to one
while student counter is less than or equal to ten
    input the next exam result  
    if the student passed</pre><p>add one to passes else add one to failures add one to student counter endif endwhile print the number of passes print the number of failures if eight or more students passed print "raise tuition" endif</p><hr><h3><strong>5.</strong></h3><pre>Larger example:  

NOTE:  NEVER ANY DATA DECLARATIONS IN PSEUDOCODE

Print out appropriate heading and make it pretty
While not EOF do:
     Scan over blanks and white space until a char is found 
	(get first character on the line)
     set can't-be-ascending-flag to 0
     set consec cntr to 1
     set ascending cntr to 1
     putchar first char of string to screen
     set read character to hold character
     While next character read != blanks and white space
          putchar out on screen
          if new char = hold char + 1
               add 1 to consec cntr
               set hold char = new char
               continue
          endif
          if new char &gt;= hold char 
               if consec cntr &lt; 3 
                    set consec cntr to 1
               endif
               set hold char = new char
               continue
          endif
          if new char &lt; hold char
               if consec cntr &lt; 3
                    set consec cntr to 1
               endif
               set hold char = new char
               set can't be ascending flag to 1
               continue
           endif
     end while
     if consec cntr &gt;= 3 
          printf (Appropriate message 1 and skip a line)
          add 1 to consec total
     endif
     if  can't be ascending flag = 0
          printf (Appropriate message 2 and skip a line)
          add 1 to ascending total
     else
          printf (Sorry message and skip a line)
          add 1 to sorry total
     endif
end While
Print out totals:  Number of consecs, ascendings, and sorries.
Stop
</pre><p>Some Keywords That Should be Used And Additional Points</p><p>For looping and selection, The keywords that are to be used include Do While...EndDo; Do Until...Enddo; While .... Endwhile is acceptable. Also, Loop .... endloop is also VERY good and is language independent. Case...EndCase; If...Endif; Call ... with (parameters); Call; Return ....; Return; When;</p><p>Always use scope terminators for loops and iteration.</p><p>As verbs, use the words Generate, Compute, Process, etc. Words such as set, reset, increment, compute, calculate, add, sum, multiply, ... print, display, input, output, edit, test , etc. with careful indentation tend to foster desirable pseudocode. Also, using words such as Set and Initialize, when assigning values to variables is also desirable.</p><p>More on Formatting and Conventions in Pseudocoding</p><ul>
<li>INDENTATION in pseudocode should be identical to its implementation in a programming language. Try to indent at least four spaces.</li>
<li>As noted above, the pseudocode entries are to be cryptic, AND SHOULD NOT BE PROSE. NO SENTENCES.</li>
<li>No flower boxes (discussed ahead) in your pseudocode.</li>
<li>Do not include data declarations in your pseudocode.</li>
<li>But do cite variables that are initialized as part of their declarations. E.g. "initialize count to zero" is a good entry.<hr>Function Calls, Function Documentation, and Pseudocode</li>
<li>Calls to Functions should appear as:
<ul>     </ul>
</li>
<li>Returns in functions should appear as:
<ul> </ul>
</li>
<li>Function headers should appear as:
<ul>     </ul>
</li>
<li>Note that in C, arguments and parameters such as "fieldn" could be written: "pointer to fieldn ...."</li>
<li>Functions called with addresses should be written as:
<ul>         </ul>
</li>
<li>Function headers containing pointers should be indicated as:
<ul>        </ul>
</li>
<li>Returns in functions where a pointer is returned:
<ul>   </ul>
</li>
<li>It would not hurt the appearance of your pseudocode to draw a line or make your function header line "bold" in your pseudocode. Try to set off your functions.</li>
<li>Try to use scope terminators in your pseudocode and source code too. It really hels the readability of the text.<hr>Source Code</li>
<li>EVERY function should have a flowerbox PRECEDING IT. This flower box is to include the functions name, the main purpose of the function, parameters it is expecting (number and type), and the type of the data it returns. All of these listed items are to be on separate lines with spaces in between each explanatory item.</li>
<li>FORMAT of flowerbox should be
<p>&nbsp;</p>
<pre>	 ********************************************************
	 Function:   ( cryptic text describing single function
		     ....... (indented like this) 	
		     .......
	 Calls:      Start listing functions "this" function calls
		     Show these functions:  one per line, indented

	 Called by:  List of functions that calls "this" function
		     Show these functions:  one per line, indented.

	 Input Parameters:  list, if appropriate; else None
	 
	 Returns:    List, if appropriate.
	 ****************************************************************
</pre>
</li>
<li>INDENTATION is critically important in Source Code. Follow standard examples given in class. If in doubt, ASK. Always indent statements within IFs, FOR loops, WILLE loops, SWITCH statements, etc. a consistent number of spaces, such as four. Alternatively, use the tab key. One or two spaces is insufficient.</li>
<li>Use scope terminators at the end of if statements, for statements, while statements, and at the end of functions. It will make your program much more readable.
<p><strong> SPELLING ERRORS ARE NOT ACCEPTABLE </strong></p>
</li>
</ul>]]></description>
	<dc:creator>Jit</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/40834/nucleus-python-and-c-code-for-reading-and-writing-genomics-data</guid>
	<pubDate>Sun, 02 Feb 2020 08:14:19 -0600</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/40834/nucleus-python-and-c-code-for-reading-and-writing-genomics-data</link>
	<title><![CDATA[Nucleus: Python and C++ code for reading and writing genomics data.]]></title>
	<description><![CDATA[<p>Nucleus is a library of Python and C++ code designed to make it easy to read, write and analyze data in common genomics file formats like SAM and VCF. In addition, Nucleus enables painless integration with the TensorFlow machine learning framework, as anywhere a genomics file is consumed or produced, a TensorFlow tfrecords file may be used instead.</p><p>Address of the bookmark: <a href="https://github.com/google/nucleus" rel="nofollow">https://github.com/google/nucleus</a></p>]]></description>
	<dc:creator>Jit</dc:creator>
</item>

<item>
  <guid isPermaLink='true'>https://bioinformaticsonline.com/opportunity/view/915/researcher-in-computer-sciencebiology</guid>
  <pubDate>Mon, 15 Jul 2013 18:38:40 -0500</pubDate>
  <link></link>
  <title><![CDATA[Researcher in computer science/biology]]></title>
  <description><![CDATA[
<p>Researcher in Computer Science at the Computational Biology Unit - temporary employment</p>

<p>The Department of Informatics is a vacant position as a researcher in computer science, related to Computational Biology Unit (CBU), for 3 years.<br /> <br />The position is part of CBU Service Group and will focus on bioinformatic analysis project and especially the analysis of high-throughput data, including NGS (sequencing), and proteomics data.<br /> <br />The successful candidate will be part of the Norwegian bioinformatics platform's national helpdesk within the project ELIXIR.NO<br /> <br />Applicants must hold a PhD in a relevant subject such as computer science, mathematics, molecular biology and also possess expertise and experience in bioinformatics statistics and analysis of data from high-throughput molecular experiment.<br /> <br />Basic programming or scripting skills are required. Experience in Python, R, Perl, Linux-based operating systems and moreover knowledge of databases and web programming will be a strength for applicants.<br /> <br />We expect enthusiasm and independence and moreover the ability to work in an interdisciplinary team environment.<br /> <br />Good knowledge of English is required.<br /> <br />Salaries start at level 57 (code 1109/LR 24.1) by appointment. Further promotion occurs after<br />service seniority in the position (at grade 57-65). Of particularly highly qualified applicants may be considered a higher salary.<br /> <br />Further information about the position is available from the chair of the CBU, <br />Professor Inge Jonassen, e-mail: Inge.Jonassen @ ii.uib.no<br /> <br />The successful applicant must comply with the guidelines that apply at any given time the position.<br /> <br />State employment shall as far as possible reflect the diversity of the population. It is therefore an objective to achieve a balanced age and sex composition and the recruitment of persons with immigrant backgrounds. Persons with immigrant background are requested to apply for the position.<br /> <br />Women are particularly encouraged to apply. If the experts find that several applicants have approximately equivalent qualifications, the rules on equal in the Personnel Regulations for Academic Positions will be applied.<br /> <br />University of Bergen applies the principles of public openness when recruiting staff to scientific positions.<br /> <br />Information about the applicant may be made public even though the applicant has requested not to be named in the list of applicants. If the request does not host admitted to the result, the applicant shall be notified of this.<br /> <br />Send application, CV, certificates, diplomas, undergraduate work and a list of publications (list of publications) online by clicking on https://www.jobbnorge.no/jobbsoknet/login.aspx?returnurl=/jobbsoknet/jobapplication.aspx?jobid=95196<br /> <br />You need to upload certified translations into English or a Scandinavian language of appendices, such as diplomas and transcripts.<br /> <br />Applications sent by email to individuals at the institute will not be considered.<br /> <br />Deadline: 9 August 2013</p>
]]></description>
</item>

</channel>
</rss>