• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

D2OL: Help me I'm new

S

Shinj1EVA

Senior member
I've decided to ditch neo. It's ridiculous :-/

Anyway, I've decided to donate my CPU cycles to process whatever d2ol wants to throw at me. Any hints/tips to squeeze the most performance out of this program?

I'll be adding 5 machines (This one's already crunching), but can I add them all to the same nick?

OK, let me kno 🙂

--Shinj1EVA
 
Excellent! Welcome to the TeAm!

When you install, each installation will ask for your email address. Use the same one for each installation.

Mastertech01 put together a great post here.

Once you have installed them, you will need to add the nodes to your user profile... it's all explained in the thread that Mastertech01 put together.

I look forward to seeing you on the MM & Stats list tomorrow!

Geoff
 
Yes... that's probably the single most important thing to do! Aside from joining the team of course! 🙂
 
welcome to the TeAm Shinj1EVA!!

Mastertech, Geoff, And AndyJones can and will answer just about any question you throw at them!!!

Happy Crunching

Slatz
 
I seem to be having problems on one machine. It's been stuck at Calculating Grid for quite some time. Since the 40th unit finished crunching anyway. Anyone know why?
 
If it stays there for a really long time (what CPU are you running?), you may have a bad candidate. What you need to do then is, assuming you are running Windows, open up Windows Explorer (not Internet Explorer), manuever your way to the SengentD2OL/D2OL/res/data/taskdata directory, right click on the structs directory and seach for the name of the candidate that you are stuck on (NCI_xxxxx*.*). You should get a folder and a few files. Shut down the engine and dspy (if you are running it), delete the folder, and start the engine back up. This effectively blows away the bad candidate 🙂
 
ah okay thanks. Well it seems to have gotten past it (finally). I have a Athlon XP 1800 on the machine it was stuck on.
 
Shouldn't stick on initializing for more than about 15 minutes on a 1800+. The more atoms & rotational bonds, the harder the candidate. 🙂
 
Here's another tip, download DSpy (found here).
I find it indispensable. Details of what it does on it's web site.
If you want to hold on to your DSpy log file, put DSpy in it's own folder, otherwise if you put it in the SengentD2OL folder and reinstall, you'll lose it 🙂
 
Originally posted by: GeoffS
Shouldn't stick on initializing for more than about 15 minutes on a 1800+. The more atoms & rotational bonds, the harder the candidate. 🙂
Click to expand...


More like less than 5 minutes or less than 2 minutes average.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top