Open PhilipDeegan opened 7 months ago
ah I seem to have mixed up hatchet
with llnl-hatchet
via pip
this is perhaps noise, tbc
the issue persists with llnl-hatchet
which I guess is a wrapper on regular hatchet
?
Hi @PhilipDeegan, do you recall how you generated your caliper data? We have instructions on our docs here: https://llnl-hatchet.readthedocs.io/en/latest/data_generation.html#caliper.
Hi @slabasan
I am using CALI_CONFIG=hatchet-sample-profile
with caliper and I get a region_profile.cali
file, using this file appears to have issues, and if I use cali-query
directly on the file it appears like an empty dataset
possibly an issue with caliper more than hatchet
Try running with CALI_LOG_VERBOSITY=1 CALI_CONFIG=hatchet-sample-profile ./app
and see if you are getting any errors. If you do hatchet-region-profile
and run cali-query on it, is the behavior the same?
I struggled with a similar issue. Eventually I tracked it down to picking up an older installed version of cali-query and using that in conjunction with my locally built caliper library. Once I matched those versions, this error went away.
Following the example on some caliper files: https://llnl-hatchet.readthedocs.io/en/latest/analysis_examples.html#read-in-a-caliper-cali-file
Fails with above error
we can see here
That a "path" is expected.
I believe this example used to work sometime ago when I tried it. It's not obvious to me how the example should be changed to have a
path
, but I am open to suggestions to test themHatchet was installed via pip for python 3.12.2
Thanks