Folding Forum

My third molecule will take 240 days to complete how do I stop it and get a smaller one one?

Welcome to the Folding forum, Lithia!

Are you running the graphical client? It likes to exaggerate quite a bit when it starts a new work unit (WU). After a couple of frames (typically, a couple of hours), the predicted number should be much more accurate.

If you still see the same estimate after a few hours, please post the relevant contents on your FAHLog.txt here.

-----
Anand

There are 4000 frames the others were 300 frames it will take about 13 weeks to run on my laptop. I tried reinstalling the program but got the same molecule back.

How long did you let it run? Just leave it alone for 2-3 hours and come back with any new numbers you see.

edit- The number of frames reported in the 5.03 GUI client don't mean much. Every other one uses 1% of the total as a "frame". Don't worry about the number of frames.

uncle fuzzy wrote:The number of frames reported in the 5.03 GUI client don't mean much. Every other one uses 1% of the total as a "frame". Don't worry about the number of frames.

The GUI client reports a ratio. If it says 6/300 frames that's 2%, just as it is if it says 500/25000 or 80/4000.

Part of the problem is that Stanford uses "frames" to mean one of two things.
First:- The number of saved checkpoints in a work unit.
Second:- The number of loops the work unit must do to finish.
If you see a frame number over 200 then its the second meaning and you'll do x number of frames per frame .........

Also sometimes the monitoring programs think the first timed checkpoint save after 15 mins ( or when ever your's is set to ) is the end of the first frame.
And will give you a silly short work unit time.
Or it will mix up frames & frames
And hence the silly long work unit time untill after its finished a couple of real frames.

Luck .............

bruce wrote:

uncle fuzzy wrote:The number of frames reported in the 5.03 GUI client don't mean much. Every other one uses 1% of the total as a "frame". Don't worry about the number of frames.

The GUI client reports a ratio. If it says 6/300 frames that's 2%, just as it is if it says 500/25000 or 80/4000.

True, but he seemed concerned about the total number of frames listed- 4000 vs. 300. That is the part I said not to worry about. The only thing the total "frames" is good for is to let you figure your progress. "Frame time" is too variable to have any consistant meaning.

I went into program files and killed the task there was little chance that the task would finish in a reasonable time. It would be nice if the program would give me the option of refusing a task. Beta writers are you listening?

lithia wrote:Beta writers are you listening?

There is little need for that. Any P3-450 running 8 hours a day will make the deadlines. Surely you are running on a computer much faster than that. And unless you answered YES to the question about getting large work units in the client setup, you already are getting small work units.

And a "resonable time" to complete a work unit varies a lot. Some work units finish in a day. Some work units finish in 10 days. The first work unit is worth 100 points, the 2nd is 1000 points. So don't get too caught up in the number of frames, etc.

I do not think the fah task is too big for your system. Just let it run.

lithia wrote:I went into program files and killed the task there was little chance that the task would finish in a reasonable time. It would be nice if the program would give me the option of refusing a task. Beta writers are you listening?

Please provide us with a little more information.

1) What was the actual assignment? If you open the file called FAHlog.txt, you'll find a history of what you've done and you should be able to find Program / Run / Clone / Gen numbers for that assignment (and the next one, if you've downloaded something else.

2) What are the specs for your computer? Speed/CPU type/Ram size/ etc.