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 am interested in processing Pilgrim traces to have some information about app performance.
I have two questions:
I would like to be able to parse events according to the grammar (for example each unique grammar of each rank). That is, in other words, iterate over events by grammar.
So far, Pilgrim2text program is iterating over all events, but is not using the RuleHash** intra_cfgs;
It remains unclear to me how to match the grammar description with both events and their duration in the trace
I tried to look at the files in the src/decoder folder but I could find something helpful.
I hope my question is clear :)
Do you have a way to access the arrays of tstarts and tends in other mode than LOSSLESS? I did not find a way to get them with Histogram (seems not supported yet according to Pilgrim2text). This one is just a bonus if you already have developed such functions.
Thank you again!
The text was updated successfully, but these errors were encountered:
Hi,
Thank you for the Pilgrim Tool. Very nice one.
I am interested in processing Pilgrim traces to have some information about app performance.
I have two questions:
I would like to be able to parse events according to the grammar (for example each unique grammar of each rank). That is, in other words, iterate over events by grammar.
So far, Pilgrim2text program is iterating over all events, but is not using the
RuleHash** intra_cfgs;
It remains unclear to me how to match the grammar description with both events and their duration in the trace
I tried to look at the files in the
src/decoder
folder but I could find something helpful.I hope my question is clear :)
Do you have a way to access the arrays of tstarts and tends in other mode than LOSSLESS? I did not find a way to get them with Histogram (seems not supported yet according to Pilgrim2text). This one is just a bonus if you already have developed such functions.
Thank you again!
The text was updated successfully, but these errors were encountered: