According to what I discussed when I requested this addition to the Rule parameters, I set up 2 complementary rules on GPUGRID to Suspend Project in the evening & Resume the next morning. It looks like each rule triggered perfectly -- once. The next day and following days, nothing. I tried opening the rules to edit and saving...no effect. I deleted the rules & built new identical ones, same thing again (once).
Am I missing something incredibly obvious :-[ to make these rules trigger every day at the '>' time, or is something broken ???
Quote from: jjwhalen on August 02, 2010, 01:30:04 AM
According to what I discussed when I requested this addition to the Rule parameters, I set up 2 complementary rules on GPUGRID to Suspend Project in the evening & Resume the next morning. It looks like each rule triggered perfectly -- once. The next day and following days, nothing. I tried opening the rules to edit and saving...no effect. I deleted the rules & built new identical ones, same thing again (once).
Am I missing something incredibly obvious :-[ to make these rules trigger every day at the '>' time, or is something broken ???
I will test this, but what times did you set for the rule, suspend and resume.
Quote from: fred on August 02, 2010, 08:34:17 AM
I will test this, but what times did you set for the rule, suspend and resume.
RULE 'GPUGRID Suspended period': >22:00:00, <06:59:59, Suspend project
RULE 'GPUGRID Active period': >07:00:00, <21:59:59, Resume project
For both I used the application name & plan class 'ACEMD2: GPU molecular dynamics (cuda31)' but left off the revision number to allow for updates.
Quote from: jjwhalen on August 02, 2010, 12:59:43 PM
Quote from: fred on August 02, 2010, 08:34:17 AM
I will test this, but what times did you set for the rule, suspend and resume.
RULE 'GPUGRID Suspended period': >22:00:00, <06:59:59, Suspend project
RULE 'GPUGRID Active period': >07:00:00, <21:59:59, Resume project
For both I used the application name & plan class 'ACEMD2: GPU molecular dynamics (cuda31)' but left off the revision number to allow for updates.
I found a bug that allows only for 00 minutes, fixed in V 0.68.
Other restrictions apply: http://www.efmer.eu/forum_tt/index.php?topic=449.msg1910#msg1910 (http://www.efmer.eu/forum_tt/index.php?topic=449.msg1910#msg1910)
Especially the first one is not going to work. Time is a strange concept. ;D
Quote from: fred on August 04, 2010, 01:55:15 PM
Quote from: jjwhalen on August 02, 2010, 12:59:43 PM
Quote from: fred on August 02, 2010, 08:34:17 AM
I will test this, but what times did you set for the rule, suspend and resume.
RULE 'GPUGRID Suspended period': >22:00:00, <06:59:59, Suspend project
RULE 'GPUGRID Active period': >07:00:00, <21:59:59, Resume project
For both I used the application name & plan class 'ACEMD2: GPU molecular dynamics (cuda31)' but left off the revision number to allow for updates.
I found a bug that allows only for 00 minutes, fixed in V 0.68.
Other restrictions apply: http://www.efmer.eu/forum_tt/index.php?topic=449.msg1910#msg1910 (http://www.efmer.eu/forum_tt/index.php?topic=449.msg1910#msg1910)
Especially the first one is not going to work. Time is a strange concept. ;D
Certainly human time is a strange concept to a computer, who lives in his own little universe of Phase1 & Phase2 clock ::) (Wikipedia (http://en.wikipedia.org/wiki/Clock_synchronization))
I actually did read the FAQ and thought I had it, but guess I blew off the part about not going past midnight. Duh :-[ An old naval communicator like me should've caught that. Will fix & (eagerly) await v0.68.
EDIT--Speaking of the FAQ and strange concepts:
Quote[FAQ] You may set another rule > 00:00:00 < 06:00:00 this rule will trigger at 00:01:00.
Has anyone else made note of the fact that if you input 00:00:00 as a rule Value, it is displayed in the Check field as a null? I'm guessing it will work fine anyway. But for the sake of clarity I used 00:00:01.
Quote from: jjwhalen on August 04, 2010, 03:02:35 PM
Certainly human time is a strange concept to a computer, who lives in his own little universe of Phase1 & Phase2 clock ::) (Wikipedia (http://en.wikipedia.org/wiki/Clock_synchronization))
I actually did read the FAQ and thought I had it, but guess I blew off the part about not going past midnight. Duh :-[ An old naval communicator like me should've caught that. Will fix & (eagerly) await v0.68.
EDIT--Speaking of the FAQ and strange concepts: Quote[FAQ] You may set another rule > 00:00:00 < 06:00:00 this rule will trigger at 00:01:00.
Has anyone else made note of the fact that if you input 00:00:00 as a rule Value, it is displayed in the Check field as a null? I'm guessing it will work fine anyway. But for the sake of clarity I used 00:00:01.
I just updated the FAQ, because I tested your settings. ;D
I will check the 0 thing.
Quote from: fred on August 04, 2010, 03:51:27 PM
Quote from: jjwhalen on August 04, 2010, 03:02:35 PM
EDIT--Speaking of the FAQ and strange concepts: Quote[FAQ] You may set another rule > 00:00:00 < 06:00:00 this rule will trigger at 00:01:00.
Has anyone else made note of the fact that if you input 00:00:00 as a rule Value, it is displayed in the Check field as a null? I'm guessing it will work fine anyway. But for the sake of clarity I used 00:00:01.
I just updated the FAQ, because I tested your settings. ;D
I will check the 0 thing.
OK I'll await further developments.
BTW I
should have said that 00:00:00 appears as a null in the Check field
before, and in the Value field
after you accept the rule.