-
Notifications
You must be signed in to change notification settings - Fork 272
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Implement CEP-2: new event container structure
- Loading branch information
Showing
71 changed files
with
1,779 additions
and
1,775 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
CEP-002 has been implemented. This is a major API breaking change, | ||
as the whole event container structure of ctapipe has been updated. | ||
|
||
The main change is the inversion of the hierarchy of telescopes | ||
and data levels. | ||
|
||
Where e.g. before the data level came first and then below that | ||
were mappings for each telescope: | ||
|
||
.. code:: python | ||
event.dl1.tel[tel_id].parameters.hillas | ||
will now become accessing first the telescope event, | ||
and then the dl1 container inside: | ||
|
||
.. code:: python | ||
event.tel[tel_id].dl1.parameters.hillas | ||
Fore more details, see :ref:`cep-002`. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.