<?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/41825?offset=20</link>
	<atom:link href="https://bioinformaticsonline.com/related/41825?offset=20" rel="self" type="application/rss+xml" />
	<description><![CDATA[]]></description>
	
	<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/pages/view/43605/installing-elgg-on-ubuntu</guid>
	<pubDate>Thu, 25 Nov 2021 01:45:59 -0600</pubDate>
	<link>https://bioinformaticsonline.com/pages/view/43605/installing-elgg-on-ubuntu</link>
	<title><![CDATA[Installing ELGG on Ubuntu !]]></title>
	<description><![CDATA[<p>Follow this:</p><h3>Settings file</h3><ul>
<li>
<div>
<div>
<div>Error</div>
<div>
<p>Your web server does not have permission to create the settings.php file in your installation directory. You have two choices:</p>
<p>1. Change the permissions on the elgg-config directory of your Elgg installation</p>
<p>2. Copy the file elgg-config/settings.example.php to elgg-config/settings.php and follow the instructions in it for setting your database parameters.</p>
</div>
</div>
</div>
</li>
</ul><p>&nbsp;</p><p>To resolve this --&nbsp;</p><p>Change the permision&nbsp;</p><p>chmod 777 elgg-config</p><h3>Web server</h3><ul>
<li>
<div>
<div>
<div>Warning</div>
<div>
<p>Your server does not support automatic testing of the rewrite rules and your browser does not support checking via JavaScript. You can continue the installation, but you may experience problems with your site. You can manually test the rewrite rules by clicking this link:&nbsp;test. You will see the word success if the rules are working.</p>
</div>
</div>
</div>
</li>
</ul><p>create a .httaccess</p><p>and provide detail in it</p><p><span style="text-decoration: underline;">Installation of Elgg</span><span></span></p><p>&nbsp;</p><p>(Note: Elgg requires&nbsp;<a href="http://www.cs.oswego.edu/~odendahl/misc/howto/mysql/">installing an instance of MySQL</a>.)</p><p>&nbsp;</p><p><span style="text-decoration: underline;">Steps to make adjustment and disposal of trial installations easier</span>.</p><p>&nbsp;</p><p><span style="text-decoration: underline;">MySQL</span></p><p>At this point, we assume you've set up your&nbsp;<tt>MySQL</tt>&nbsp;database</p><div><ol>
<li>Start your&nbsp;<tt>mysqld</tt>&nbsp;server daemon.<br />(For the sake of this example, we'll assume we're running on port 9999; you shouldn't actually use this port because only one daemon can run on any port number.)</li>
<li>Login to the server as&nbsp;<tt>root</tt>&nbsp;user, using the&nbsp;<tt>mysql</tt>&nbsp;client.</li>
<li>Create a database to store Elgg's tables. We'll call the database&nbsp;<tt>elggalpha</tt>.<br /><tt>mysql&gt; create database elggalpha;</tt></li>
<li>Grant access to a user &mdash; for this example we'll call him/her&nbsp;<tt>elggalphauser</tt>.
<pre>mysql&gt; grant all privileges on elggalpha.* to 'elggalphauser'@'moxie'
    -&gt; identified by 'secretpassword';
</pre>
</li>
</ol></div><p>&nbsp;</p><p><span style="text-decoration: underline;">Elgg</span></p><p>&nbsp;</p><div><ol>
<li>Type&nbsp;<tt>umask 022</tt></li>
<li>Change into your&nbsp;<tt>public_html</tt>&nbsp;directory (<em>aka</em>&nbsp;folder).<br /><tt>cd public_html</tt></li>
<li>make a directory called&nbsp;<tt>elgg</tt><br /><tt>mkdir elgg</tt></li>
<li>Change into the&nbsp;<tt>elgg</tt>&nbsp;subdirectory of&nbsp;<tt>public_html</tt>.<br /><tt>cd elgg</tt></li>
<li>download elgg into this directory</li>
<li>you'll end up with a file named<br /><tt>/home/<em>your-user-id</em>/public_html/elgg/elgg-X.X.X.X.zip</tt><br />(It's not literally&nbsp;<tt>X.X.X.X</tt>, it might be&nbsp;<tt>elgg-1.8.0.1.zip</tt>, for example.)</li>
<li>unzip elgg<br /><tt>unzip -q elgg-1.8.0.1.zip</tt></li>
<li>you'll end up with a directory (folder) named<br /><tt>/home/<em>your-user-id</em>/public_html/elgg/elgg-X.X.X.X</tt></li>
<li>make a symbolic link (<em>aka</em>&nbsp;shortcut) to this<br /><tt>ln -s elgg-X.X.X.X alpha</tt><br />(For example,&nbsp;<tt>ln -s elgg-1.8.0.1 alpha</tt>)</li>
<li>Give user&nbsp;<tt>nobody</tt>&nbsp;access to this directory<br /><tt>/usr/misc/bin/acl.sh -r -u nobody elgg-1.8.0.1</tt></li>
<li>create a data directory for&nbsp;<tt>elgg</tt>&nbsp;(get into your home directory first):
<pre>cd
mkdir -p elgg/alpha/data
chmod -R 755 elgg/alpha/data
</pre>
</li>
<li>Change into the&nbsp;<tt>elgg/alpha</tt>&nbsp;directory.<br /><tt>cd elgg/alpha</tt></li>
<li>Give user&nbsp;<tt>nobody</tt>&nbsp;access to this subdirectory&nbsp;<tt>data</tt><br /><tt>/usr/misc/bin/acl.sh -u nobody data</tt></li>
<li>In your browser, navigate to your elgg installation<br /><tt>http://moxie.cs.oswego.edu/~<em>your-user-id</em>/elgg/alpha/</tt><br />You'll have a screen which includes this message:
<pre>Welcome

Installing Elgg has 6 simple steps and reading this welcome is the first one!

If you haven't already, read through the installation instructions included with Elgg (or click the instructions link at the bottom of the page).

If you are ready to proceed, click the Next button.
</pre>
</li>
<li>Follow configuration process:
<ul>
<li>The first screen probably will contain a success message in green and a failure message in pink:
<pre><span>Requirements check</span>

Your server failed the requirements check. After you have fixed the below issues, refresh this
page. Check the troubleshooting links at the bottom of this page if you need further assistance.
<span>PHP</span></pre>
<div>Your server's PHP satisfies all of Elgg's requirements.</div>
<pre>
<span>Web server</span></pre>
<div>We think your server is running the Apache web server. The rewrite test failed and the most likely cause is that AllowOverride is not set to All for Elgg's directory. This prevents Apache from processing the .htaccess file which contains the rewrite rules. A less likely cause is Apache is configured with an alias for your Elgg directory and you need to set the RewriteBase in your .htaccess. There are further instructions in the .htaccess file in your Elgg directory.</div>
<pre>
<span>Database</span></pre>
<div>The database requirements are checked when Elgg loads its database.</div>
</li>
<li>To correct this, replace the&nbsp;<tt>.htaccess</tt>&nbsp;file that Elgg created with one that you can edit:
<pre>cp -ip .htaccess temp-htaccess
rm .htaccess
mv temp-htaccess .htaccess
</pre>
</li>
<li>Edit the&nbsp;<tt>.htaccess</tt>&nbsp;file: Go to approximately line 101 (where it says&nbsp;<tt>#RewriteBase /</tt>) and add the line:<br /><tt>RewriteBase /~<em>your-user-id</em>/elgg/alpha/</tt></li>
<li>Be sure to save the edited file.
<p>&nbsp;</p>
<p>&nbsp;</p>
</li>
<li>Click the&nbsp;<span>Refresh</span>&nbsp;button.
<p>&nbsp;</p>
<p>&nbsp;</p>
</li>
<li>If this hasn't fixed things, seek professional help.
<p>&nbsp;</p>
<p>&nbsp;</p>
</li>
<li>Click the&nbsp;<span>Next</span>&nbsp;button.
<p>&nbsp;</p>
<p>&nbsp;</p>
</li>
<li>Fill in the parameters appropriate to your MySQL installation.
<pre><span>Database installation</span>

If you haven't already created a database for Elgg, do that now. Then fill in the values below to
initialize the Elgg database.

<span>Database Username</span></pre>
<div>elggalphauser</div>
<pre>User that has full priviledges to the MySQL database that you created for Elgg

<span>Database Password</span></pre>
<div>secretpassword</div>
<pre>Password for the above database user account

<span>Database Name</span></pre>
<div>elggalpha</div>
<pre>Name of the Elgg database

<span>Database Host</span></pre><sup>&Dagger;</sup>
<div>moxie:9999</div>
<pre>Hostname of the MySQL server (usually localhost)
<strong>&Dagger;You might need to use <tt>127.0.0.1:9999</tt> for the host
    if you haven't set up MySQL as we've done.</strong>



<span>Database Table Prefix</span></pre>
<div>elgg_</div>
<pre>The prefix given to all of Elgg's tables (usually elgg_)
</pre>
<div><span>Next</span></div>
<p>&nbsp;</p>
<p>&nbsp;</p>
</li>
<li>Continue filling in forms as requested.
<pre>Configure site</pre>
<div>Database has been installed.</div>
<pre>
We need some information about the site as we configure Elgg. If you haven't created a data directory for Elgg, you need to do so now.

<span>Site Name</span></pre>
<div>My Elgg Site version Alpha</div>
<pre>The name of your new Elgg site

<span>Site Email Address</span></pre>
<div><em>your-user-id</em>@oswego.edu</div>
<pre>Email address used by Elgg for communication with users

<span>Site URL</span></pre>
<div>http://moxie.cs.oswego.edu/~<em>your-user-id</em>/elgg/alpha/</div>
<pre>The address of the site (Elgg usually guesses this correctly)

<span>Elgg Install Directory</span></pre>
<div>/home/<em>your-user-id</em>/public_html/elgg/elgg.1.8.0.1/</div>
<pre>The directory where you put the Elgg code (Elgg usually guesses this correctly)

<span>Data Directory</span></pre>
<div>/home/<em>your-user-id</em>/elgg/alpha/data</div>
<pre>The directory that you created for Elgg to save files (the permissions on this directory are checked
when you click Next)

<span>Default Site Access</span></pre>
<div>Public</div>
<pre>The default access level for new user created content
</pre>
</li>
<li>
<pre><span>Create admin account</span></pre>
<div>Site settings have been saved.</div>
<pre>
It is now time to create an administrator's account.

<span>Display Name</span></pre>
<div>&nbsp;</div>
<pre>The name that is displayed on the site for this account

<span>Email Address</span></pre>
<div>&nbsp;</div>
<pre>
<span>Username</span></pre>
<div>&nbsp;</div>
<pre>Account username used for logging in

<span>Password</span></pre>
<div>&nbsp;</div>
<pre>Account password must be at least 6 characters long

<span>Password Again</span></pre>
<div>&nbsp;</div>
<pre>Retype password to confirm</pre>
</li>
</ul>
</li>
</ol></div>]]></description>
	<dc:creator>Jit</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/blog/view/44762/stay-connected-and-productive-unlock-the-power-of-screen-tmux-and-mosh-for-bioinformatics</guid>
	<pubDate>Wed, 22 Jan 2025 00:29:52 -0600</pubDate>
	<link>https://bioinformaticsonline.com/blog/view/44762/stay-connected-and-productive-unlock-the-power-of-screen-tmux-and-mosh-for-bioinformatics</link>
	<title><![CDATA[Stay Connected and Productive: Unlock the Power of Screen, Tmux, and Mosh for Bioinformatics]]></title>
	<description><![CDATA[<p>If you are a bioinformatician, chances are you have spent hours running long, complex analyses on remote servers only to lose your session because of an unstable connection. Frustrating, isnt it? Fear not! With tools like <strong>screen</strong>, <strong>tmux</strong>, and <strong>mosh</strong>, you can safeguard your workflow and stay productive, no matter where you are.</p><h4>Why Remote Session Management is a Must-Have</h4><p>In bioinformatics, tasks like genome assembly, RNA-seq analyses, and phylogenetic computations often take hours or days. A dropped SSH connection can result in:</p><ul>
<li><strong>Lost Progress:</strong> Restarting a job from scratch wastes valuable time.</li>
<li><strong>Workflow Interruptions:</strong> Disruptions can derail your focus and productivity.</li>
<li><strong>Corrupted Data:</strong> Interrupted processes may lead to incomplete or corrupted outputs.</li>
</ul><p>By integrating <strong>screen</strong>, <strong>tmux</strong>, or <strong>mosh</strong> into your workflow, you can avoid these setbacks and ensure a seamless experience.</p><h4>Screen: The Classic Workhorse</h4><p><strong>Screen</strong> is a terminal multiplexer that comes pre-installed on most Linux systems. It allows you to manage multiple terminal sessions and reconnect to them even after being disconnected.</p><p><strong>Getting Started with Screen:</strong></p><ol>
<li><strong>Start a Session:</strong>
<div>
<div>
<div>
<div>screen</div>
</div>
</div>
</div>
</li>
<li><strong>Detach from a Session:</strong><br />Press <code>Ctrl+A</code>, then <code>D</code>.</li>
<li><strong>Reattach to a Session:</strong>
<div>
<div>
<div>
<div>screen -r</div>
</div>
</div>
</div>
</li>
</ol><p><strong>Pro Tip:</strong> Enhance your screen experience with a customized <code>.screenrc</code> configuration file. Download one here: <a href="https://lnkd.in/es8vhcEH" target="_new">Get .screenrc</a>.</p><h4>Tmux: A Modern Alternative</h4><p><strong>Tmux</strong> takes everything great about screen and adds modern features, including better key bindings and intuitive session management. It\u2019s perfect for bioinformaticians who want more control over their workflow.</p><p><strong>Getting Started with Tmux:</strong></p><ol>
<li><strong>Start a Session:</strong>
<div>
<div>
<div>
<div>tmux</div>
</div>
</div>
</div>
</li>
<li><strong>Detach from a Session:</strong><br />Press <code>Ctrl+B</code>, then <code>D</code>.</li>
<li><strong>Reattach to a Session:</strong>
<div>
<div>
<div>
<div>tmux attach</div>
</div>
</div>
</div>
</li>
</ol><p><strong>Customize Your Tmux Experience:</strong><br />Use a <code>.tmux.conf</code> file to personalize your setup. Grab one here: <a href="https://lnkd.in/eZZfxmq7" target="_new">Download .tmux.conf</a>.</p><h4>Mosh: The Mobile Shell for Unreliable Connections</h4><p>SSH works well for stable networks, but it struggles in areas with spotty connectivity. Enter <strong>Mosh</strong>, the Mobile Shell. Designed for intermittent networks, Mosh keeps your session alive even when the connection drops temporarily.</p><p><strong>Why Mosh is a Game-Changer:</strong></p><ul>
<li>No lag over high-latency networks.</li>
<li>Automatically reconnects when the network is restored.</li>
<li>Ideal for working on the go, from cafes to trains.</li>
</ul><p><strong>Getting Started with Mosh:</strong></p><ol>
<li><strong>Install Mosh:</strong>
<div>
<div>
<div>
<div>sudo apt install mosh # For Debian/Ubuntu</div>
</div>
</div>
</div>
</li>
<li><strong>Connect to a Server:</strong>
<div>
<div>
<div>
<div>mosh username@server</div>
</div>
</div>
</div>
</li>
</ol><p>Learn more at <a href="https://mosh.org" target="_new">mosh.org</a>.</p><h4>Why This Matters for Bioinformatics</h4><p>Every bioinformatician knows the value of time and data integrity. Tools like screen, tmux, and mosh provide a lifeline when running long analyses, enabling you to:</p><ul>
<li>Safeguard your work against disconnections.</li>
<li>Easily manage multiple workflows in parallel.</li>
<li>Stay productive, even in challenging environments.</li>
</ul><h4>Quickstart Cheat Sheet</h4><ul>
<li>
<p><strong>Screen:</strong></p>
<div>
<div>
<div>
<div>screen # Start a session Ctrl+A, D # Detach screen -r # Reattach</div>
</div>
</div>
</div>
</li>
<li>
<p><strong>Tmux:</strong></p>
<div>
<div>tmux <span># Start a session </span> Ctrl+B, D <span># Detach </span> tmux attach <span># Reattach</span></div>
</div>
</li>
<li>
<p><strong>Mosh:</strong></p>
<div>
<div>mosh username@server</div>
</div>
</li>
</ul><h4>Final Thoughts</h4><p>As a bioinformatician, your time is too valuable to spend restarting analyses due to technical hiccups. With screen, tmux, and mosh in your toolkit, you can work smarter, protect your progress, and stay productive no matter where you are. Start using these tools today and transform the way you work with remote systems.</p><p>Let me know how these tools work for you, and don\u2019t forget to follow for more bioinformatics tips!</p>]]></description>
	<dc:creator>BioStar</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/38908/busca-an-integrative-web-server-to-predict-subcellular-localization-of-proteins</guid>
	<pubDate>Thu, 07 Feb 2019 14:08:11 -0600</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/38908/busca-an-integrative-web-server-to-predict-subcellular-localization-of-proteins</link>
	<title><![CDATA[BUSCA: an integrative web server to predict subcellular localization of proteins]]></title>
	<description><![CDATA[<p><span>BUSCA (Bologna Unified Subcellular Component Annotator) is a web-server for predicting protein subcellular localization. BUSCA integrates different tools to predict localization-related protein features (DeepSig, TPpred3, PredGPI and ENSEMBLE3.0) as well as tools for discriminating subcellular localization of both globular and membrane proteins (BaCelLo, MemLoci and SChloro).</span></p><p>Address of the bookmark: <a href="http://busca.biocomp.unibo.it/" rel="nofollow">http://busca.biocomp.unibo.it/</a></p>]]></description>
	<dc:creator>BioStar</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/41565/csar-web-a-web-server-of-contig-scaffolding-using-algebraic-rearrangements</guid>
	<pubDate>Fri, 10 Apr 2020 04:39:36 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/41565/csar-web-a-web-server-of-contig-scaffolding-using-algebraic-rearrangements</link>
	<title><![CDATA[CSAR-web: a web server of contig scaffolding using algebraic rearrangements]]></title>
	<description><![CDATA[<p><span>CSAR-web is a web-based tool that allows the users to efficiently and accurately scaffold (i.e. order and orient) the contigs of a target draft genome based on a complete or incomplete reference genome from a related organism.&nbsp;</span></p>
<p><span><span>CSAR-web can serve as a convenient and useful scaffolding tool allowing the users to efficiently and accurately scaffold their draft genomes according to a complete or incomplete reference genome.&nbsp;</span></span></p><p>Address of the bookmark: <a href="http://genome.cs.nthu.edu.tw/CSAR-web" rel="nofollow">http://genome.cs.nthu.edu.tw/CSAR-web</a></p>]]></description>
	<dc:creator>BioStar</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/blog/view/43911/slurm-commands</guid>
	<pubDate>Wed, 06 Jul 2022 07:40:07 -0500</pubDate>
	<link>https://bioinformaticsonline.com/blog/view/43911/slurm-commands</link>
	<title><![CDATA[SLURM Commands]]></title>
	<description><![CDATA[<h3>SLURM commands</h3><p>The following table shows SLURM commands on the SOE cluster.</p><table border="1">
<thead>
<tr><th>Command</th><th>Description</th></tr>
</thead>
<tbody>
<tr>
<td><strong>sbatch</strong></td>
<td>Submit batch scripts to the cluster</td>
</tr>
<tr>
<td><strong>scancel</strong></td>
<td>Signal jobs or job steps that are under the control of Slurm.</td>
</tr>
<tr>
<td><strong>sinfo</strong></td>
<td>View information about SLURM nodes and partitions.</td>
</tr>
<tr>
<td><strong>squeue</strong></td>
<td>View information about jobs located in the SLURM scheduling queue</td>
</tr>
<tr>
<td><strong>smap</strong></td>
<td>Graphically view information about SLURM jobs, partitions, and set configurations parameters</td>
</tr>
<tr>
<td><strong>sqlog</strong></td>
<td>View information about running and finished jobs</td>
</tr>
<tr>
<td><strong>sacct</strong></td>
<td>View resource accounting information for finished and running jobs</td>
</tr>
<tr>
<td><strong>sstat</strong></td>
<td>View resource accounting information for running jobs</td>
</tr>
</tbody>
</table><p><span>For more information, run&nbsp;</span><strong>man</strong><span>&nbsp;on the commands above. See some examples below.</span><br /><br /><span style="font-size: large;"><strong>1. Info about the partitions and nodes</strong></span><span></span><br /><span>List all the partitions available to you and the nodes therein:</span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>sinfo
</pre>
</td>
</tr>
</tbody>
</table></div><p><span>Nodes in state&nbsp;</span><tt>idle</tt><span>&nbsp;can accept new jobs.</span><br /><br /><span>Show a partition configuratuin, for example,&nbsp;</span><tt>SOE_main</tt><span></span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>scontrol show partition=SOE_main
</pre>
</td>
</tr>
</tbody>
</table></div><p><span>Show current info about a specific node:</span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>scontrol show node=&lt;nodename&gt;
</pre>
</td>
</tr>
</tbody>
</table></div><p><span>You can also specify a group of nodes in the command above. For example, if your MPI job is running across soenode05,06,35,36, you can execute the command below to get the info on the nodes you are interested in:</span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>scontrol show node=soenode[05-06,35-36]
</pre>
</td>
</tr>
</tbody>
</table></div><p><span>An informative parameter in the output to look at would be CPULoad. It allows you to see how your application utilizes the CPUs on the running nodes.</span><br /><br /><span style="font-size: large;"><strong>2. Submit scripts</strong></span><span></span><br /><span>The header in a submit script specifies job name, partition (queue), time limit, memory allocation, number of nodes, number of cores, and files to collect standard output and error at run time, for example</span></p><div><table border="1">
<tbody>
<tr>
<td>
<pre>#!/bin/bash

#SBATCH --job-name=OMP_run     # job name, "OMP_run"
#SBATCH --partition=SOE_main   # partition (queue)
#SBATCH -t 0-2:00              # time limit: (D-HH:MM) 
#SBATCH --mem=32000            # memory per node in MB 
#SBATCH --nodes=1              # number of nodes
#SBATCH --ntasks-per-node=16   # number of cores
#SBATCH --output=slurm.out     # file to collect standard output
#SBATCH --error=slurm.err      # file to collect standard errors
</pre>
</td>
</tr>
</tbody>
</table></div><p><span>If the time limit is not specified in the submit script, SLURM will assign the default run time, 3 days. This means the job will be terminated by SLURM in 72 hrs. The maximum allowed run time is two weeks,&nbsp;</span><tt>14-0:00</tt><span>.</span><br /><span>If the memory limit is not requested, SLURM will assign the default 16 GB. The maximum allowed memory per node is 128 GB. To see how much RAM per node your job is using, you can run commands&nbsp;</span><tt>sacct</tt><span>&nbsp;or&nbsp;</span><tt>sstat</tt><span>&nbsp;to query MaxRSS for the job on the node - see examples below.</span><br /><span>Depending on a type of application you need to run, the submit script may contain commands to create a temporary space on a computational node -&nbsp;</span><a href="http://ecs.rutgers.edu/file_systems.html">see the discussion about using the file systems on the cluster.</a><span></span><br /><span>Then it sets the environment specific to the application and starts the application on one or multiple nodes - see sbatch sample scripts in directory&nbsp;</span><tt>/usr/local/Samples</tt><span>&nbsp;on soemaster1.hpc.rutgers.edu.</span><br /><span>You can submit your job to the cluster with&nbsp;</span><tt>sbatch</tt><span>&nbsp;command:</span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>sbatch myscript.sh
</pre>
</td>
</tr>
</tbody>
</table></div><p><br /><span style="font-size: large;"><strong>3. Query job information</strong></span><span></span><br /><span>List all currently submitted jobs in running and pending states for a user:</span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>squeue -u &lt;username&gt;
</pre>
</td>
</tr>
</tbody>
</table></div><p><span>Command&nbsp;</span><tt>squeue</tt><span>&nbsp;can be run with format options to expose specific information, for example, when pending job #706 is scheduled to start running:</span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>squeue -j 706 --format="%S"
</pre>
</td>
</tr>
</tbody>
</table></div><div><table border="1">
<tbody>
<tr>
<td>
<pre>START_TIME
2015-04-30T09:54:32
</pre>
</td>
</tr>
</tbody>
</table></div><p><span>More info can be shown by placing additional format options, for example:</span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>squeue -j 706 --format="%i %P %j %u %T %l %C %S"
</pre>
</td>
</tr>
</tbody>
</table></div><div><table border="1">
<tbody>
<tr>
<td>
<pre>JOBID PARTITION   NAME    USER STATE   TIMELIMIT  CPUS START_TIME
706   SOE_main  Par_job_3 mike PENDING 3-00:00:00 64   2015-04-30T09:54:32
</pre>
</td>
</tr>
</tbody>
</table></div><p><span>To see when all the jobs, pending in the queue, are scheduled to start:</span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>squeue --start 
</pre>
</td>
</tr>
</tbody>
</table></div><p><br /><span>List all running and completed jobs for a user</span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>sqlog -u &lt;username&gt;
</pre>
</td>
</tr>
</tbody>
</table></div><p><span>or</span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>sqlog -j &lt;JobID&gt;
</pre>
</td>
</tr>
</tbody>
</table></div><p><span>The following appreviations are used for the job states:</span></p><pre>       CA   CANCELLED      Job was cancelled.

       CD   COMPLETED      Job completed normally.

       CG   COMPLETING     Job is in the process of completing.

       F    FAILED         Job termined abnormally.

       NF   NODE_FAIL      Job terminated due to node failure.

       PD   PENDING        Job is pending allocation.

       R    RUNNING        Job currently has an allocation.

       S    SUSPENDED      Job is suspended.

       TO   TIMEOUT        Job terminated upon reaching its time limit.
</pre><p><span>You can specify the fields you would like to see in the output of&nbsp;</span><tt>sqlog</tt><span>:</span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>sqlog --format=list
</pre>
</td>
</tr>
</tbody>
</table></div><p><span>The command below, for example, provides Job ID, user name, exit state, start date-time, and end date-time for job #2831:</span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>sqlog -j 2831 --format=jid,user,state,start,end
</pre>
</td>
</tr>
</tbody>
</table></div><p><span>List status info for a currently running job:</span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>sstat -j &lt;jobid&gt;
</pre>
</td>
</tr>
</tbody>
</table></div><p><span>A formatted output can be used to gain only a specific info, for example, the maximum resident RAM usage on a node:</span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>sstat --format="JobID,MaxRSS" -j &lt;jobid&gt;
</pre>
</td>
</tr>
</tbody>
</table></div><p><span>To get statistics on completed jobs by jobID:</span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>sacct --format="JobID,JobName,MaxRSS,Elapsed" -j &lt;jobid&gt;
</pre>
</td>
</tr>
</tbody>
</table></div><p><span>To view the same information for all jobs of a user:</span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>sacct --format="JobID,JobName,MaxRSS,Elapsed" -u &lt;username&gt;
</pre>
</td>
</tr>
</tbody>
</table></div><p><span>To print a list of fields that can be specified with the&nbsp;</span><tt>--format</tt><span>&nbsp;option:</span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>sacct --helpformat
</pre>
</td>
</tr>
</tbody>
</table></div><p><span>For example, to get Job ID, Job name, Exit state, start date-time, and end date-time for job #2831:</span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>sacct -j 2831 --format="JobID,JobName,State,Start,End"
</pre>
</td>
</tr>
</tbody>
</table></div><p><span>Another useful command to gain information about a running job is&nbsp;</span><tt>scontrol</tt><span>:</span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>scontrol show job=&lt;jobid&gt;
</pre>
</td>
</tr>
</tbody>
</table></div><p><br /><span style="font-size: large;"><strong>4. Cancel a job</strong></span><span></span><br /><span>To cancel one job:</span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>scancel &lt;jobid&gt;
</pre>
</td>
</tr>
</tbody>
</table></div><p><span>To cancel one job and delete the TMP directory created by the submit script on a node:</span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>sdel &lt;jobid&gt;
</pre>
</td>
</tr>
</tbody>
</table></div><p><span>To cancel all the jobs for a user:</span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>scancel -u &lt;username&gt;
</pre>
</td>
</tr>
</tbody>
</table></div><p><span>To cancel one or more jobs by name:</span></p><div><table border="0" style="background-color: #D0D0D0;">
<tbody>
<tr>
<td>
<pre>scancel --name &lt;myJobName&gt;
</pre>
</td>
</tr>
</tbody>
</table></div>]]></description>
	<dc:creator>Shruti Paniwala</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/31014/sockeye</guid>
	<pubDate>Fri, 17 Feb 2017 08:51:16 -0600</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/31014/sockeye</link>
	<title><![CDATA[sockeye]]></title>
	<description><![CDATA[<p>This sockeye&nbsp;software uses the Ensembl database project to import sequence and annotation information from several eukaryotic species. A user can additionally import their own custom sequence and annotation data. Individual annotation objects are displayed in Sockeye by using custom 3D models. Ensembl-derived and imported sequences can be analyzed by using a suite of multiple and pair-wise alignment algorithms. The results of these comparative analyses are also displayed in the 3D environment of Sockeye. By using the Java3D API to visualize genomic data in a 3D environment, we are able to compactly display cross-sequence comparisons. This provides the user with a novel platform for visualizing and comparing genomic feature organization.</p><p>Address of the bookmark: <a href="http://www.bcgsc.ca/platform/bioinfo/software/sockeye/releases/1.3" rel="nofollow">http://www.bcgsc.ca/platform/bioinfo/software/sockeye/releases/1.3</a></p>]]></description>
	<dc:creator>Jit</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/38212/megahit-an-ultra-fast-single-node-solution-for-large-and-complex-metagenomics-assembly-via-succinct-de-bruijn-graph</guid>
	<pubDate>Wed, 14 Nov 2018 04:50:27 -0600</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/38212/megahit-an-ultra-fast-single-node-solution-for-large-and-complex-metagenomics-assembly-via-succinct-de-bruijn-graph</link>
	<title><![CDATA[MEGAHIT: an ultra-fast single-node solution for large and complex metagenomics assembly via succinct de Bruijn graph]]></title>
	<description><![CDATA[<p><span>MEGAHIT is a single node assembler for large and complex metagenomics NGS reads, such as soil. It makes use of succinct&nbsp;</span><em>de Bruijn</em><span>&nbsp;graph (SdBG) to achieve low memory assembly. MEGAHIT can&nbsp;</span><span>optionally</span><span>&nbsp;utilize a CUDA-enabled GPU to accelerate its SdBG contstruction. The GPU-accelerated version of MEGAHIT has been tested on NVIDIA GTX680 (4G memory) and Tesla K40c (12G memory) with CUDA 5.5, 6.0 and 6.5. MEGAHIT v1.0 or greater also supports IBM Power PC and has been tested on IBM POWER8.</span></p>
<p><span>https://academic.oup.com/bioinformatics/article/31/10/1674/177884</span></p><p>Address of the bookmark: <a href="https://github.com/voutcn/megahit" rel="nofollow">https://github.com/voutcn/megahit</a></p>]]></description>
	<dc:creator>Jit</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/41957/majiq-2-is-released</guid>
	<pubDate>Thu, 09 Jul 2020 03:06:26 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/41957/majiq-2-is-released</link>
	<title><![CDATA[MAJIQ 2 is released !]]></title>
	<description><![CDATA[<p>&nbsp;</p>
<p>Ability to detect, quantify, and visualize complex and de-novo splicing variations from RNASeq.</p>
<p>MAJIQ&rsquo;s accuracy compares favorably to other algorithms.</p>
<p>MAJIQ 2 is *way* faster, more memory and I/O efficient</p>
<p>New visualization (VOILA 2.0) Ability to analyze hundreds and thousands of samples Why so negative? (Support for a confident negative set)</p>
<p><span>Finally, a major reason we are excited about MAJIQ 2.0 is that it sets the code base for many new exciting algorithmic and visualization improvements, with application to new research questions so stay tuned!</span></p>
<p><span>More at <a href="https://biociphers.wordpress.com/2019/04/01/majiq-2-is-out/">https://biociphers.wordpress.com/2019/04/01/majiq-2-is-out/</a></span></p><p>Address of the bookmark: <a href="https://majiq.biociphers.org/" rel="nofollow">https://majiq.biociphers.org/</a></p>]]></description>
	<dc:creator>LEGE</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/pages/view/1897/genetic-test-in-india</guid>
	<pubDate>Sun, 11 Aug 2013 10:54:35 -0500</pubDate>
	<link>https://bioinformaticsonline.com/pages/view/1897/genetic-test-in-india</link>
	<title><![CDATA[Genetic Test in India]]></title>
	<description><![CDATA[<p>1.<strong>Xcode Life Sciences Pvt. Ltd.</strong><br /><span>6B, Eldorado,&nbsp;</span><br /><span>112, Nungambakkam High Road,</span><br /><span>Nungambakkam, Chennai 600034</span><br /><span>Tamil Nadu, India&nbsp;</span></p><p>2.<span><strong>Mapmygenome&trade;</strong><br /></span><span>Royal Demeure,HUDA Techno Enclave,<br />Plot No. 12/2, Sector-1 500 081&nbsp;<br />Madhapur,Hyderabad<br />AP, India</span></p><p>3.<strong>&nbsp;DNA Labs India</strong></p><p><strong><a href="http://www.dnalabsindia.com/lab.php">http://www.dnalabsindia.com/lab.php</a></strong></p><p>&nbsp;</p><p>4.<strong>MedGenome Labs Pvt Ltd</strong><br /><span>(Division of SciGenom Labs Pvt Ltd.)</span><br /><span>Plot no: 43A,SDF, 3rd floor</span><br /><span>A Block,CSEZ, Kakanad, Cochin</span><br /><span>Kerala - 682037&nbsp;</span><br /><span>Phone: 0484 - 2413399</span><br /><span>Fax: 0484 - 2413398</span><br /><span>Email:&nbsp;</span><a href="mailto:info@medgenome.com">info@medgenome.com</a></p><p>5.<strong>Narayana Nethralaya</strong></p><p><span>Narayana Hrudayalaya Campus</span><br /><span>Narayana Health City</span><br /><span># 258/A, Bommasandra, Hosur Road,&nbsp;</span><br /><span>Bangalore - 560 099 - INDIA.</span><br /><span>TEL: +91-80-66660655-0658&nbsp;</span><br /><span>FAX: +91-80-66660650&nbsp;</span><br /><span>Mobile: 9902 821128 (Emergency Only)</span><br /><span>e-mail:&nbsp;</span><a href="mailto:info@narayananethralaya.com">info@narayananethralaya.com</a></p><p>6.<strong>BioAxis DNA Research Centre Private Limited</strong><br />13-51,Sri Lakshmi Nagar colony,<br />Besides Big Bazar, Near Kamineni Hospitals<br />GSI Post BandalGuda (L B Nagar) Hydeabad-500068<br />Andhra Pradesh (<strong>India</strong>).<br />Phone :&nbsp;+91-40-24034503/+91-9246338983</p><p>7.<strong>Gene Guiide</strong></p><p>8th Floor, Embassy Towers, 7 Bungalows Rd, Versova, Andheri West, Mumbai-61&nbsp;<br />&nbsp;09167 117799&nbsp;<br />&nbsp;<a href="mailto:info@geneguiide.com" target="_blank">info@geneguiide.com</a>&nbsp;</p><p>See more at: http://www.geneguiide.com</p><p>8.<strong>INDIAN BIOSCIENCES</strong><br />Regd. Office:<br />G-2 (Ground Floor Rear), Kailash Colony, New Delhi - 110048, India.<br />Phone: +91 (0)11 29236088, Email: info@inbdna.com.</p><p>9.<strong>SRL Limited</strong></p><p>GP-26, MARUTI INDUSTRIAL ESTATE,</p><p>UDYOG VIHAR,SECTOR-18,</p><p>GURGAON - 122015</p><p>Tel: 0124-3001243 / 0124-3001209</p><p><strong>SRL Limited</strong><br />VASANT VIHAR, 8, PALAM MARG,<br />NEW DELHI - 110057<br />Tel: 011 - 4229 5333&nbsp;</p><p><strong>Website:</strong>&nbsp;<a href="http://www.srlworld.com/" target="_blank">http://www.srlworld.com</a><br /><strong>National Customer care number:</strong><br />Call Toll Free : 1800-222-660/1800-102-8282&nbsp;<br /><strong>E-mail id:</strong>&nbsp;<a href="mailto:customercare@srl.in">customercare@srl.in</a></p><p>10.<strong>Tata Memorial Centre</strong>,</p><p>Advanced Centre for Treatment, Research and Education in Cancer</p><p>Kharghar, Navi Mumbai - 410 210, INDIA.</p><p>Tel: +91-22-2740 5000</p><p>Fax: +91-22-2740 5085</p><p>E-mail: mail@actrec.gov.in</p><p style="text-align: center;">&nbsp;</p><p style="text-align: center;"><span style="font-size: large;"><a href="mailto:office@actrec.gov.in"></a></span></p><p>&nbsp;</p>]]></description>
	<dc:creator>Rahul Agarwal</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/news/view/4590/tigers-genome-sequenced</guid>
	<pubDate>Tue, 17 Sep 2013 16:48:24 -0500</pubDate>
	<link>https://bioinformaticsonline.com/news/view/4590/tigers-genome-sequenced</link>
	<title><![CDATA[Tigers genome sequenced]]></title>
	<description><![CDATA[<p>Fifteen scientists led by Dr Jong Bhak of Genome Research Foundation, South Korea, decoded as many as 3 billion nucleotides (organic molecules that form the basic building blocks of nucleic acids, such as DNA). They identified 20,000 genes related to various functions of the tiger.&nbsp;</p><p>The biggest and perhaps most fearsome of the world's big cats, the tiger, shares 95.6 percent of its DNA with humans' cute and furry companions, domestic cats.</p><p>The new research showed that big cats have genetic mutations that enabled them to be carnivores. The team also identified mutations that allow snow leopards to thrive at high altitudes.</p><p>Reference:</p><p><a href="http://www.nbcnews.com/science/your-cat-ferocious-tigers-share-lot-95-6-percent-their-4B11182690">http://www.nbcnews.com/science/your-cat-ferocious-tigers-share-lot-95-6-percent-their-4B11182690</a></p><p><a href="http://timesofindia.indiatimes.com/home/environment/flora-fauna/Gene-mapping-of-tiger-completed/articleshow/22671681.cms">http://timesofindia.indiatimes.com/home/environment/flora-fauna/Gene-mapping-of-tiger-completed/articleshow/22671681.cms</a></p><p>Paper:</p><p><a href="http://www.nature.com/ncomms/2013/130917/ncomms3433/full/ncomms3433.html">http://www.nature.com/ncomms/2013/130917/ncomms3433/full/ncomms3433.html</a></p>]]></description>
	<dc:creator>Rahul Agarwal</dc:creator>
</item>

</channel>
</rss>