GV Question(s)

[Mark F]

I remember somebody posted with a link to a thread in another (non-MURC) forum in which MashRinx (the creator of GV; who I just passed on the user stats whoo Hooo!) talkes about some of the upcomeing changes in the next version.
Also, if anyone has any info on when it might come out (maybe from another source)?

Thanks,
Mark F.

Feel free to use this thread for any other questions or info on GV.

------------------
OH NO, my retractable cup holder swallowed a DVD...
and burped out a movie

[Liquid Snake]

Are you referring to <A HREF="http://www.dslreports.com/forum/remark,600419;root=folding;mode=flat#603906">this</A>?

[Mark F]

Well not the thread I rememberd, but it had the info I was looking for. Thanx again

[Jorden]

I've got a problem with GV. And am wondering if I am the only one

When I run a unit in the background in GV, Gv at one point tries to tell me the sequence is at 40%, while the actual sequence is running at 80% or more.

Anyone else noticed this?

Jord.

[Rattledagger]

Well, I don't know that file GV checks, but output.out counts two times to 15.

As I've understood it, Genome first uses rotamers.lib for the 15 first sequences, afterwards a shorter, reduced.tmp on the last 15. If you used the first genome-client, this counted to 15 and afterwards started again counting 2, 4, ...

[Mark F]

I think GV just guess based on How long whole sequences take. That could be why it needs 2 seq. to start counting. Once it's counting you can staop the Client and GV will keep counting. It stops when it gets to 100% of a seq. , and waits. Also if a seq. finishes before the GV counter gets to 100%, GV 'knows' about it right away. Hence my guess, about GV just guessing based on what it can know, such as when a seq is done.


------------------
Mark F. (A+ & Network+)
--------------------------------------------------
OH NO, my retractable cup holder swallowed a DVD...
and burped out a movie