search

jakesylvestre / cing

Automatically exported from code.google.com/p/cing
0 stars 0 forks source link

Further tailor the report that CING generates #209

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Allow for a full run or a quickie.

This is different from setting the verbosity and it's also different from 
yes/no generating imagery.

This would limit the analyses run and thus potentially affect the overall 
scores.

Charles can you specify what you would like to see come out on this?

-1- Do only an XML file with per residue ROGs?
-2- Would it be ok to take a little longer and still run all checks, terse and 
without imagery?
-3- Can you recommend parallelization approaches for a multi-node setup like 
you have in Xplor-
NIH?

Original issue reported on code.google.com by jurge...@gmail.com on 28 Oct 2009 at 9:38

GoogleCodeExporter commented 8 years ago 
I'm relaying Charles' message below. I got it as a bounced message:
From: <Charles@schwieters.org>
To: <cing@googlecode.com>
Anyway:

Hello Jurgen--

>
> Charles can you specify what you would like to see come out on this?
>
> -1- Do only an XML file with per residue ROGs?

probably easy to smallish, easy to understand plaintext or images would
be better. The idea being that a quick perusal of some cing results be
possible. If the user has interest, a more complete cing run can be
performed. I expect that the amount of output should be tunable from
within the Xplor-NIH script.

> -2- Would it be ok to take a little longer and still run all checks,
> terse  and without imagery?

again, this should be tunable. But I'm not certain about default levels
until I get things working a bit.

> -3- Can you recommend parallelization approaches for a multi-node
> setup  like you have in Xplor-
> NIH?

It should be possible to use the structure-level parallelism so that
cing is run on compute nodes for each structure. This certainly is my
intention.

Original comment by jurge...@gmail.com on 30 Oct 2009 at 9:35

GoogleCodeExporter commented 8 years ago 
I think Geerten's new XML summary file is a good first attempt at addressing 
the issue. Let me know when you 
guys need more.

Original comment by jurge...@gmail.com on 8 Feb 2010 at 12:55