Schedule criterion

[Tom Krowka]

Having a problem with criterion selection on schedules. Have several zones, each with a different name. Using conditions, I am trying to get only the zones I want in the schedule.
At the right end of the criterion line, there is a plus sign. I am under the impression that + button allows one to duplicate the criterion and set further conditions. Can I only set different conditions, or can I duplicate the condition and use different values. Does not seem to work that way.

Also, using the <> condition. I thought that would exclude all names with that started with a particular value. In this case HEATED. Have several zones that start with HEATED, but it does not remove them from the schedule.

Also tried just the letter H, that did not work either.


Tried it the other way, by including everything in the schedule except heated. Did this by duplicating the criterion and using ".x." and one word from every name. That gave me a totally blank screen.

I think there is some bug in the schedule if you try to use more than one value for the same criterion. Or something.

[Karl Ottenstein]

This question belongs in the Calculate Forum (moderator: please move?).

Yes, + adds new conditions.

No, <> does not exclude 'starting with' ... <> means NOT EQUAL. The criterion will include all zones whose name is not the precise string "HEATED".

The x.. is for 'starts with', ..x is for 'ends with'. Etc.

Post a screenshot of your criterion list if you're still stuck, Tom. 😉

Karl

[Tom Krowka]

OK got that about the <> I thought it would exclude anything that would be within the brackets, did not realize it would search for the characters as a complete string only.

[Tom Krowka]

The + sign adds new conditions for each criterion selected.

Can I add more than one variable to one criterion, perhaps separated by a comma or a space?

[Tom Krowka]

It seems the scheduler does not quite work as advertised. I am using the <> condition. Using Zone Name criterion, <> condition, I type in the whole string, which is "heated first floor'" exactly as typed in the zone name. Then I hit OK, and it disappears from the schedule, as it should.

Then I hit the plus sign, which should be a duplicate of the the zone name. Then again using <> condition, is type in the zone name of "heated second floor" exactly as typed in the zone name. Now I have two zone names.

I hit OK, neither of them are removed from the schedule, both are still in the schedule.

I guess I could put those two on a different layer and remove them from the schedule that way, but I don't think I should have to use a workaround for this simple situation. Seems pretty straightforward.

[Karl Ottenstein]

Well, Tom, it looks like you've found a functionality problem with the I.S.

Without testing to confirm the general case, take a look at the attached snippet from the User Guide page 332 (PDF from installation CD if printed manual not handy).

The first example treats the additional comparisons as if they are joined by a logical AND operation: (story >=0) AND (story <=2)

The second example treats the additional comparisons is if joined by a logical OR: (story=0) OR (story=1) OR (story=2).

It cannot be both, or in this example, it cannot be interpretted by GS as an AND or OR based on what they THINK the user wants. [Actually I think this is their logic on logic: if there are multiple "=" conditions, then they cannot be linked by AND since nothing can be equal to more than one thing; therefore, they use the OR operator. I think they assume an AND operation for all other operators. What they do with a combination of other operators and "=", I don't want to take the time to test!]


We need to have the option of specifying the operator. (Well, we really need to be able to place fully parenthesized expressions in a pinch, since the criteria-as-allowed are limiting for any but the most common schedules.)

The workaround for you seems to be to prefix (or suffix) the zones that you DO want with something that you can filter on with x.. or ..x, or to list every zone (!) with an "=" as in the story example, or...

[It's a shame that there is no way to negate the x.. or ..x conditions, in order to select things that do NOT begin or end with some text.]

Karl

[Tom Krowka]

Karl:

I had to read your reply several times to get the idea of the whole and/or thing. Not sure I really have it, but I'm working on it. Too convoluted for Monday morning.

My workaround is to put the heated and non heated spaces on different layers.

Thanks for the info.