You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think these are the only Dynamo related events that can be measured fairly reliably...
Launching Dynamo JournalCommand via ribbon:
Jrn.Command "Ribbon" , "Launch Dynamo , ID_VISUAL_PROGRAMMING_DYNAMO"
JournalCommand via keyboard shortcut:
Jrn.Command "KeyboardShortcut" , "Launch Dynamo , ID_VISUAL_PROGRAMMING_DYNAMO"
There's a JournalTimeStamp in the previous line and JournalMemoryMetrics in the following line or one line after that.
So we can take the timestamp of that block and the first memory metrics we find in that block.
Shutting down Dynamo
Shutdown is completed once we see this JournalAPIMessage:
' 1:< API_SUCCESS { Unregistering Idling event by application Dynamo For Revit (8d83c886-b739-4acd-a9db-1bc78f315b2b). }
There's usually a JournalTimeStamp right after that, so basically the time stamp of the next block.
Launching Dynamo Player JournalCommand via ribbon:
Jrn.Command "Ribbon" , "Launch Dynamo Playlist , ID_FILE_TOPOSURFACE_LINK"
JournalCommand via keyboard shortcut:
Jrn.Command "KeyboardShortcut" , "Launch Dynamo Playlist , ID_FILE_TOPOSURFACE_LINK"
:-) Interesting command ID...
There's a JournalTimeStamp in the previous line and JournalMemoryMetrics in the following line or one line after that.
So we can take the timestamp of that block and the first memory metrics we find in that block.
Note that this will always be followed up by another call to Dynamo Player (JournalCommand as keyboard shortcut) - I suppose this may mark the first time a script is played.
Shutting down Dynamo Player
Undetectable since it's not a Revit addin per se
The previous line has the JournalTimeStamp and there's JournalMemoryMetrics and JournalGUIResourceUsage info directly before it and after the JournalAddinEvent.
Again, the previous line has the JournalTimeStamp. After a JournalComment there's the JournalMemoryMetrics and JournalGUIResourceUsage info.
Running a script in automatic mode
Only the end of execution will be marked with a JournalData line (see above), but that block does not necessarily contain any JournalMemoryMetrics.
Running a script in Dynamo Player
Only the end of execution will be marked with a JournalData line (see above), that block usually also contains a JournalMemoryMetrics line.
The text was updated successfully, but these errors were encountered:
I think these are the only Dynamo related events that can be measured fairly reliably...
Launching Dynamo
JournalCommand
via ribbon:JournalCommand
via keyboard shortcut:There's a
JournalTimeStamp
in the previous line andJournalMemoryMetrics
in the following line or one line after that.So we can take the timestamp of that block and the first memory metrics we find in that block.
Shutting down Dynamo
Shutdown is completed once we see this
JournalAPIMessage
:There's usually a
JournalTimeStamp
right after that, so basically the time stamp of the next block.Launching Dynamo Player
JournalCommand
via ribbon:JournalCommand
via keyboard shortcut::-) Interesting command ID...
There's a
JournalTimeStamp
in the previous line andJournalMemoryMetrics
in the following line or one line after that.So we can take the timestamp of that block and the first memory metrics we find in that block.
Note that this will always be followed up by another call to Dynamo Player (
JournalCommand
as keyboard shortcut) - I suppose this may mark the first time a script is played.Shutting down Dynamo Player
Undetectable since it's not a Revit addin per se
Running a script in manual mode
Start:
The previous line has the
JournalTimeStamp
and there'sJournalMemoryMetrics
andJournalGUIResourceUsage
info directly before it and after theJournalAddinEvent
.End:
In Dynamo 1.0:
In Dynamo 1.3:
Again, the previous line has the
JournalTimeStamp
. After aJournalComment
there's theJournalMemoryMetrics
andJournalGUIResourceUsage
info.Running a script in automatic mode
Only the end of execution will be marked with a
JournalData
line (see above), but that block does not necessarily contain anyJournalMemoryMetrics
.Running a script in Dynamo Player
Only the end of execution will be marked with a
JournalData
line (see above), that block usually also contains aJournalMemoryMetrics
line.The text was updated successfully, but these errors were encountered: