Fix looping over omgeo maps

[pweigel]

In icetray v1.13.0, an old method of accessing maps was removed, which affects looping over the om geometries.

This PR just changes some loops over frame["I3Geometry"].omgeo since they used the removed method and no longer work with the latest version of icetray.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (master@b314abd). Learn more about missing BASE report.

Additional details and impacted files

@@           Coverage Diff            @@
##             master     #29   +/-   ##
========================================
  Coverage          ?   0.04%           
========================================
  Files             ?      34           
  Lines             ?    4239           
  Branches          ?     817           
========================================
  Hits              ?       2           
  Misses            ?    4236           
  Partials          ?       1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mhuen]

Thanks for creating the PR and fixing this. I'll merge once the print statement is removed.

[mhuen]

Do the older icetray versions support this indexing? Otherwise I think we will need to add some compatibility for that

[pweigel]

Oops, that was from some testing I was doing earlier.

As far as I understand, the .items() method should have always worked and should be backward compatible. The old __iter__ method for these objects acted like a std::map/similar to .items() and yielded the tuples rather than acting like a python dictionary (just the keys). Here is the icetray PR that changed this behavior: https://github.com/icecube/icetray/pull/3576

[mhuen]

Ok, then this should be good to go