| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 4
|
|
| Author |
|
|
n7zfi
Cruncher Joined: Apr 9, 2006 Post Count: 2 Status: Offline Project Badges:
|
Hi,
I am seeing text in work unit results that are marked as 'Pending Verification' or 'Inconclusive' that are simular to the following: AG Check: Found receptor.A.map Beginning AutoDock... INFO: Setting num_generations: 27000 Setting maxGen to 6750 autodock4: WARNING: Unrecognized keyword in docking parameter file, in line: compute_unbound_extended # compute extended ligand energyAbout to enter main loop...(dockings already completed: 9) I am concerned about the line that warns about an invalid keyword. Is this really a bad thing? Is there anything I can do to correct it? I am running the BOINC client v. 5.4.9. on each of the three systems where I am seeing this on occasion. Thanks! Jim |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello n7zfi,
Clicking on the VALID status in my Results Status page for FAAH work units, I find the same message. So apparently it is not a problem. Lawrence |
||
|
|
Alther
Former World Community Grid Tech United States of America Joined: Sep 30, 2004 Post Count: 414 Status: Offline Project Badges:
|
Hi, I am seeing text in work unit results that are marked as 'Pending Verification' or 'Inconclusive' that are simular to the following: AG Check: Found receptor.A.map Beginning AutoDock... INFO: Setting num_generations: 27000 Setting maxGen to 6750 autodock4: WARNING: Unrecognized keyword in docking parameter file, in line: compute_unbound_extended # compute extended ligand energyAbout to enter main loop...(dockings already completed: 9) I am concerned about the line that warns about an invalid keyword. Is this really a bad thing? Is there anything I can do to correct it? Jim This is fine. This means AutoDock ran into a keyword (compute_unbound_extended) in one of its parameter files it did not understand. It's harmless and can be ignored. It's just logged for information purposes. That's why it is logged as only a warning and not as an error ![]()
Rick Alther
Former World Community Grid Developer |
||
|
|
n7zfi
Cruncher Joined: Apr 9, 2006 Post Count: 2 Status: Offline Project Badges:
|
Thanks for the reassurance. As a network admin, warnings usually make me wonder what I'm missing. It's alway good news when I can safely ignore them.
|
||
|
|
|