Streaming: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 14: | Line 14: | ||
Ben about 'no hits' debugging: | Ben about 'no hits' debugging: | ||
The vtpStats() function (I think that's what it's called) that shows MIG Writes and Read is a good indicator it's building hits - so that'll be a good thing to check if you aren't seeing hits in data to see if that shows anything (we can estimate the event builder hit rate on the VTP based on the number of MIG writes & reads per second). Let me know if you'd like me to try in debug something (particularly if you have it in a weird state: if you can leave it in that state I can try to login to check). | The vtpStats() function (I think that's what it's called) that shows MIG Writes and Read is a good indicator it's building hits - so that'll be a good | ||
thing to check if you aren't seeing hits in data to see if that shows anything (we can estimate the event builder hit rate on the VTP based on the number | |||
of MIG writes & reads per second). Let me know if you'd like me to try in debug something (particularly if you have it in a weird state: if you can leave | |||
it in that state I can try to login to check). | |||
Latest revision as of 10:39, 29 July 2026
Streaming data format
Raw data from VTP: png
Aggregated data: png
git ???
VTP library checkout:
cd $CODA/src/ git
Ben about 'no hits' debugging:
The vtpStats() function (I think that's what it's called) that shows MIG Writes and Read is a good indicator it's building hits - so that'll be a good thing to check if you aren't seeing hits in data to see if that shows anything (we can estimate the event builder hit rate on the VTP based on the number of MIG writes & reads per second). Let me know if you'd like me to try in debug something (particularly if you have it in a weird state: if you can leave it in that state I can try to login to check).