Activity (RSS)

(from [ad0affbef1794d6b2efc9971e9604da8a63c28c2]) Rename/reorder the menu options to have a better flow. Update css to make the menu more readable. Change the l...

I agree that it should be fixed to be more useful to someone besides myself or another developer.

In making the movie showing how to use Vipdac, I noticed that the order of the menu items on the left hand side doesnt follow the most likely use by a researche...

The filenames need to be uniquely named due to the S3 storage method(single key per file), but we can come up with a better way to display the data for the user...

We need a better way to present the results files that we have at the moment. Concatenating the job name, database and other params makes for an unreadable piec...

Based on testing, the OMSSA code needs to be fixed for no enzyme searches before this makes a significant difference.

This has been added to the newest ami.

This was added into the current ami.

-no minimum size of peptides for no-enzyme and semi-tryptic searches -nox maximum size of peptides for no-enzyme and semi-tryptic searches

Add parameters to 'no enzyme' and 'semi-tryptic enzyme' options.

If you realize you made a mistake in a job that's been launched, you need to be able to delete it.

Right now, the queue system doesn't allow that to happen, sin...

Some searches can be run quickly on a large database, which will create a sub-database upon which a more detailed search can be run.

This should significantly s...

To allow result files to be deleted and analyzed easier, create a separate model/controller to allow their download and removal as needed. We can also persist t...

Changing the name to split the data file and result file issues into 2 tickets.

This is part of the statistics for the csv file analysis.

This feature is important from the standpoint that it will parallel the creation of a results file model/controller that will allow the data and results files t...

This is basing the assumption that you're running on a single node. It does give you the instance id and process id of the worker that processed the chunk. It w...

In the short term it is possible to just copy the table of data from the page and paste into Excel so that would work just fine to get the data out.

It still mi...

For development/testing it would be nice to be able to download the stats for a given job - essentially dump out the data on the jobs/1 page. If there was also ...

When you are creating a new job all you can see for the parameter file is the name that someone used when they saved it. It might be nice to have some way to re...

It seems that AWS can throw an error if you try to create a node and it doesn't have capacity.

The user will see the default 500 error page, but going forward i...

I've moved the "show" links for anything that has a show option to the name or ID of that item.

When the job is finished, the download link will appear next to ...

added a meta refresh tag for the job index and show pages which will refresh the pages every 15 seconds.

The new build has graphics for the "new" links.

It would be nice to track some information about the cluster for a given job - how many nodes were going when it started and what type of nodes they were. This ...

Is it worth having some ajax-y autorefresh on the jobs pages so that the progress keeps updating if there are active jobs, without the user having to hit refres...

The two text links on the /jobs/list page are very close together - show and delete. It seems like it might be too easy to hit the delete link by mistake. I did...

The text links to New Job, New parameter File, etc are rather inconspicuous on their respective pages. The most likely reason that people visit these pages is t...

I'm doing some testing and want to run different analyses on the same dataset, ie the .mgf file is the same but the parameters might be different (or in this ca...

The system will now check if the access and secret keys are part of the user data. If not, it will symlink an error page as the index informing the user of the ...

If the user doesn't enter the proper information in the user data section, we need to inform them of this issue since the instance they launched will not work.

Based on the performance of SimpleDB this far, I would not suggest using it as the database backend.

Also, the use of a common database backend will be an issue...

Brian will be updating the documentation when he collects screenshots for the paper. I'll confirm this with him.

I thought it was something like that. Lets update the documentation so its clear how to do this using the AWS console - I thought I did it correctly but clearly...

It seems that the user data wasn't properly set when launching the instance. The system threw this error RightAws::AwsError: AWS access keys are required to ope...

I fired up the new AMI using the console with the access and secret keys in the user data section of the advanced options, as per the original docs.

The instanc...

This has been added as of the 1/27/09 image.

This has been added as of the 1/27/09 image.

Let the head node decide how many workers to launch/keep active based on the available workload.