jabaws

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
this looks like the same pattern of scheduler settings as in ServiceStatus - if you wanted to be more Java-ish, you'd have a generic ScheduledEventAttribute class that manipulated a given servlet c...

this looks like the same pattern of scheduler settings as in ServiceStatus - if you wanted to be more Java-ish, you'd have a generic ScheduledEventAttribute class that manipulated a given servlet context's attributes to create/update these stats

  • More
  • CR-2
  • started review
JWS-121: Service status and usage statistics show cached results for faster loads
JWS-121: Service status and usage statistics show cached results for faster loads
I guess Geoff only wants updated looks here, so I guess this could be an improvement as well.

I guess Geoff only wants updated looks here, so I guess this could be an improvement as well.

So Geoff does not want JPred to included in the next release. My understanding is that if Jabaws 2.1 includes a previous version of Jpred, it should be removed...

So Geoff does not want JPred to included in the next release. My understanding is that if Jabaws 2.1 includes a previous version of Jpred, it should be removed...

Thanks Jim Procter! Gonna read it and get my way around. Also, I am going to remove the file, was more to see whether the pushing was working...

Thanks Jim Procter! Gonna read it and get my way around. Also, I am going to remove the file, was more to see whether the pushing was working...

  • More
  • CR-1
  • finished reviewing
Rather than create cryptic .txt files in the jabaws source repository (where they will stay forever), I suggest you instead use the JWS Jira project. We have some (now slightly out of date) notes ...

Rather than create cryptic .txt files in the jabaws source repository (where they will stay forever), I suggest you instead use the JWS Jira project.

We have some (now slightly out of date) notes on how the jalview team does this on the wiki. The take home message, however, is that before you start coding, or whatever, use the issue tracker to decide what to code/write/fix, and log your progress. You may even discover issues that you wanted to fix that have already been lodged by someone else !

Remember: If it doesn't happen on the bug tracker, then it hasn't happened yet

No, really.

For more info see: https://wiki.jalview.org/index.php/Development#Pick_something_to_work_on_from_issues.jalview.org

I suspect an epic is called for here, since there will be a number of issues for each tool

I suspect an epic is called for here, since there will be a number of issues for each tool

Again, this should be a new, separate issue.

Again, this should be a new, separate issue.

Suggest you create an epic to collect issues for improving the stats page (or create a component and a series of issues tagged to it)

Suggest you create an epic to collect issues for improving the stats page (or create a component and a series of issues tagged to it)

Is this for downloading JABAWS ? Again, you should create an 'Improvement' on the JWS project to tag this - since it goes into the release notes for the updated version

Is this for downloading JABAWS ?

Again, you should create an 'Improvement' on the JWS project to tag this - since it goes into the release notes for the updated version

Suggest you create a task for this

Suggest you create a task for this

  • More
  • CR-1
  • started review
Added a new document for logging the goals and todos (work in progress)
Added a new document for logging the goals and todos (work in progress)
Merge branch 'JWS-27-jronn' into JABAWS_Release_2_0

JWS-27 replaced JRonn with patched biojava 3.0.4 version which runs correctly for large sets of sequences in multithreaded mode

    • binary
    /binaries/windows/bj3.0.4p-jronn.jar
    • -0
    • +4
    /binaries/windows/bj3.0.4p-jronn.jar.readme
    • -0
    • +23
    /binaries/windows/bj3.0.4p-jronn.patch
Merge branch 'JWS-29' into JABAWS_Release_2_0

JWS-29 patch fixes bug - wierd workaround since "^\\s*>" caused scanner to advance to end of file rather than start of next FASTA header

test demonstrating JWS-29 assertion failure

Merge branch 'JWS-36' into JABAWS_Release_2_0

JWS-36 patched Scores writer to put spaces between ranges and space separated scores

    • -5
    • +6
    /datamodel/compbio/data/sequence/Score.java
Merge branch 'JWS-35' into JABAWS_Release_2_0

patch fixes JWS-35

test for JWS-35 - check that range and first value of prediction for each method matches expected values

remove jabaws 3 development code

    • -152
    • +0
    /engine/compbio/engine/cluster/dundee/_Queue.java
    • -121
    • +0
    /engine/compbio/engine/conf/_Key.java
    • -134
    • +0
    /runner/compbio/pipeline/_jpred/BlastParser.java
  1. … 30 more files in changeset.
ensure we never check in autogenerated documentation or build artefacts

fix jabaws download link

word order

git-svn-id: link to svn.lifesci.dundee.ac.uk/svn/barton/ptroshin/JABA2@4814 e3abac25-378b-4346-85de-24260fe3988d

load the driver explicitly

git-svn-id: link to svn.lifesci.dundee.ac.uk/svn/barton/ptroshin/JABA2@4813 e3abac25-378b-4346-85de-24260fe3988d

AMI ID update

git-svn-id: link to svn.lifesci.dundee.ac.uk/svn/barton/ptroshin/JABA2@4809 e3abac25-378b-4346-85de-24260fe3988d