Deciphering logs (Condition #29, Statement #30, etc)


#1

I can’t find any documentation in the wiki, so hopefully I can find some enlightenment here.

As I’m building a piston, I find it essential to observe how statements evaluated, scheduled or cancelled. So far I’m using logging level ‘full’, but the details seem generic (at least to me).

Here’s an example:
+851ms ║║Condition #29 evaluated false (10ms)
+862ms ║║Condition #33 evaluated false (10ms)
+871ms ║║Condition #36 evaluated false (7ms)
+872ms ║║Cancelling condition #16’s schedules…
+873ms ║║Condition group #16 evaluated false (state changed) (34ms)
+884ms ║║Comparison (boolean) false is (boolean) false = true (3ms)
+886ms ║║Condition #14 evaluated true (9ms)
+941ms ║║Comparison (enum) idle did_not_change = false (45ms)
+943ms ║║Condition #27 evaluated false (54ms)
+944ms ║║Condition group #26 evaluated false (state did not change) (56ms)
+946ms ║║Condition group #17 evaluated false (state did not change) (70ms)
+951ms ║║Cancelling statement #30’s schedules…

Is there a way to tell what is Condition #29, or Condition group #26, or Statement #30 in my actual piston? I thought the numbers would match up to a line number in the piston but that isn’t the case.


#2

Turn on Trace (blue switch I think) and you’ll see the numbers in gray or is that grey…


#3

You are amazing! It shows the colored column bars like in legacy CoRE, too, which I wanted.

Thanks!


#11

Moved to Piston Design Help category.
More appropriate place for it, but marked as solved.

-Housekeeping