Difference between revisions of "PASA"

From UFRC
Jump to navigation Jump to search
m (Text replace - "Usage policy" to "Usage Policy")
(24 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
 
__NOEDITSECTION__
 
__NOEDITSECTION__
[[Category:Software]][[Category:Bioinformatics]][[Category:Genomics]]
+
[[Category:Software]][[Category:Biology]][[Category:Genomics]][[Category:NGS]]
<!-- ########  Template Configuration ######## -->
+
{|<!--Main settings - REQUIRED-->
<!--Edit definitions of the variables used in template calls
 
Required variables:
 
app - lowercase name of the application e.g. "amber"
 
url - url of the software page (project, company product, etc) - e.g. "http://ambermd.org/"
 
Optional variables:
 
INTEL - Version of the Intel Compiler e.g. "11.1"
 
MPI - MPI Implementation and version e.g. "openmpi/1.3.4"
 
-->
 
{|
 
<!--Main settings - REQUIRED-->
 
 
|{{#vardefine:app|pasa}}
 
|{{#vardefine:app|pasa}}
 
|{{#vardefine:url|http://pasa.sourceforge.net/}}
 
|{{#vardefine:url|http://pasa.sourceforge.net/}}
<!--Compiler and MPI settings - OPTIONAL -->
 
|{{#vardefine:intel|}} <!-- E.g. "11.1" -->
 
|{{#vardefine:mpi|}} <!-- E.g. "openmpi/1.3.4" -->
 
<!--Choose sections to enable - OPTIONAL-->
 
|{{#vardefine:mod|1}} <!--Present instructions for running the software with modules -->
 
 
|{{#vardefine:exe|1}} <!--Present manual instructions for running the software -->
 
|{{#vardefine:exe|1}} <!--Present manual instructions for running the software -->
 
|{{#vardefine:conf|}} <!--Enable config wiki page link - {{#vardefine:conf|1}} = ON/conf|}} = OFF-->
 
|{{#vardefine:conf|}} <!--Enable config wiki page link - {{#vardefine:conf|1}} = ON/conf|}} = OFF-->
Line 34: Line 19:
  
 
The Program to Assemble Spliced Alignments (PASA) is used to automatically incorporate ESTs and full-length cDNAs into gene structure annotations, in the process annotating UTRs, alternative splicing variations, and polyadenylation sites.
 
The Program to Assemble Spliced Alignments (PASA) is used to automatically incorporate ESTs and full-length cDNAs into gene structure annotations, in the process annotating UTRs, alternative splicing variations, and polyadenylation sites.
 
+
<!--Modules-->
==Available Versions==
+
==Environment Modules==
* 20110520
+
Run <code>module spider {{#var:app}}</code> to find out what environment modules are available for this application.
<!-- -->
+
See [[Modules|modules documentation]] for details.
{{#if: {{#var: mod}}|==Execution Environment and Modules==
+
==System Variables==
{{App_Module|app={{#var:app}}|intel={{#var:intel}}|mpi={{#var:mpi}}}}|}}
+
* HPC_{{uc:{{#var:app}}}}_DIR - installation directory
 
* HPC_PASA_BIN - executable directory.
 
* HPC_PASA_BIN - executable directory.
 
* HPC_PASA_CONF - config file directory.
 
* HPC_PASA_CONF - config file directory.
{{#if: {{#var: exe}}|==How To Run==
+
<!--Additional-->
 +
{{#if: {{#var: exe}}|==Additional Information==
 
===Tools and variables===
 
===Tools and variables===
 
* <code>UNIVECDB</code> environment variable is set to the location of the UniVec database for use by seqclean.
 
* <code>UNIVECDB</code> environment variable is set to the location of the UniVec database for use by seqclean.
 +
 +
===Database Removal Policy===
 +
See [[Database_Removal_Procedure|the Database Removal Procedure]] for details on how application databases are removed or retained by UFRC.
 +
 
===Databases===
 
===Databases===
* The MySQL server used by PASA has been configured to allow the pasaadmin user to create databases with names that end in _pasa only. So, to run pasa your configuration file such as alignAssembly.config or conf.txt must have MySQL configuration similar to the following entry:
+
;Note that we have a single DB server that supports all applications that make use of databases. Use [[SLURM Job Arrays]] and throttle you jobs to at most 10 active tasks at a time to avoid overwhelming it.
  MYSQLDB=test_run_pasa
+
 
 +
 
 +
The MySQL server used by PASA has been configured to allow the pasaadmin user to create databases with names in the form of "pasa_${USER}_". So, to run pasa your configuration file such as alignAssembly.config or conf.txt must have MySQL configuration similar to the following entry:
 +
  MYSQLDB=pasa_jdoe_run1
 +
 
 +
The example configuration files are located in $HPC_PASA_CONF directory.
 +
 
 +
Make sure to name your pasa database as 'pasa_${USER}_$NAME' where '$NAME' is the name you want to give the database and '$USER' is your username. For example a database can be named as 'pasa_jdoe_experiment_1'.
 +
 
 +
Please contact us if you would like to prevent automatic removal of old pasa databases. We may remove all databases over six months old.
 +
 
 +
Use helper tools we created for managing PASA databases. The following tools are available:
 +
 
 +
* rc_list_pasa_databases
 +
: List all databases named pasa_% on the server
 +
* rc_create_pasa_db NAME
 +
: Create an empty database with name 'NAME'. Name your databases as shown above
 +
* rc_export_pasa_db NAME
 +
: Save your PASA database named 'NAME' to a file named 'NAME.sql' in the current working directory. Use this to backup databases, so they don't get lost in a cleanup if you may need them later.
 +
* rc_import_pasa_db NAME.sql
 +
: Create a database called 'NAME' and import structure and data from an sql file called 'NAME.sql'
 +
* rc_remove_pasa_db
 +
: Remove a database you no longer need from the server.
  
The example configuration files are located in <code>/apps/pasa/20110520/pasa_conf</code> ($HPC_PASA_CONF) directory.
 
 
|}}
 
|}}
 
===Web Portal===
 
===Web Portal===
You can visualize the results of your PASA run by going to the "http://pasa.hpc.ufl.edu/cgi-bin/status_report.cgi?db=$MYSQL_DB" URL where "$MYSQL_DB" must be changed to the database name used for the run. Use your HPC credentials to access the protected web portal.
+
You can visualize the results of your PASA run by going to "http://pasa2.rc.ufl.edu/cgi-bin/status_report.cgi?db=$MYSQL_DB" URI where "$MYSQL_DB" must be changed to the database name used for the run. Use your HPC credentials to access the protected web portal.
 +
 
 +
Note: Pasa2 web interface no longer has an administrative page. Go directly to status_report.cgi.
 +
 
 +
Pasa 1.5 URIs can be reached at http://pasa.rc.ufl.edu.
 
{{#if: {{#var: conf}}|==Configuration==
 
{{#if: {{#var: conf}}|==Configuration==
 
See the [[{{PAGENAME}}_Configuration]] page for {{#var: app}} configuration details.|}}
 
See the [[{{PAGENAME}}_Configuration]] page for {{#var: app}} configuration details.|}}

Revision as of 16:57, 21 August 2022

Description

pasa website  

The Program to Assemble Spliced Alignments (PASA) is used to automatically incorporate ESTs and full-length cDNAs into gene structure annotations, in the process annotating UTRs, alternative splicing variations, and polyadenylation sites.

Environment Modules

Run module spider pasa to find out what environment modules are available for this application. See modules documentation for details.

System Variables

  • HPC_PASA_DIR - installation directory
  • HPC_PASA_BIN - executable directory.
  • HPC_PASA_CONF - config file directory.

Additional Information

Tools and variables

  • UNIVECDB environment variable is set to the location of the UniVec database for use by seqclean.

Database Removal Policy

See the Database Removal Procedure for details on how application databases are removed or retained by UFRC.

Databases

Note that we have a single DB server that supports all applications that make use of databases. Use SLURM Job Arrays and throttle you jobs to at most 10 active tasks at a time to avoid overwhelming it.


The MySQL server used by PASA has been configured to allow the pasaadmin user to create databases with names in the form of "pasa_${USER}_". So, to run pasa your configuration file such as alignAssembly.config or conf.txt must have MySQL configuration similar to the following entry:

MYSQLDB=pasa_jdoe_run1

The example configuration files are located in $HPC_PASA_CONF directory.

Make sure to name your pasa database as 'pasa_${USER}_$NAME' where '$NAME' is the name you want to give the database and '$USER' is your username. For example a database can be named as 'pasa_jdoe_experiment_1'.

Please contact us if you would like to prevent automatic removal of old pasa databases. We may remove all databases over six months old.

Use helper tools we created for managing PASA databases. The following tools are available:

  • rc_list_pasa_databases
List all databases named pasa_% on the server
  • rc_create_pasa_db NAME
Create an empty database with name 'NAME'. Name your databases as shown above
  • rc_export_pasa_db NAME
Save your PASA database named 'NAME' to a file named 'NAME.sql' in the current working directory. Use this to backup databases, so they don't get lost in a cleanup if you may need them later.
  • rc_import_pasa_db NAME.sql
Create a database called 'NAME' and import structure and data from an sql file called 'NAME.sql'
  • rc_remove_pasa_db
Remove a database you no longer need from the server.

Web Portal

You can visualize the results of your PASA run by going to "http://pasa2.rc.ufl.edu/cgi-bin/status_report.cgi?db=$MYSQL_DB" URI where "$MYSQL_DB" must be changed to the database name used for the run. Use your HPC credentials to access the protected web portal.

Note: Pasa2 web interface no longer has an administrative page. Go directly to status_report.cgi.

Pasa 1.5 URIs can be reached at http://pasa.rc.ufl.edu.