3.10.1.5.1.7.1.1. opengate.contrib.tps.ionbeamtherapy¶
3.10.1.5.1.7.1.1.1. Attributes¶
3.10.1.5.1.7.1.1.2. Classes¶
This class reads a DICOM 'RT Ion Plan Storage' file and collects related information such as TPS dose files. |
|
3.10.1.5.1.7.1.1.3. Functions¶
|
|
|
|
|
|
|
|
|
|
|
3.10.1.5.1.7.1.1.4. Module Contents¶
- opengate.contrib.tps.ionbeamtherapy.sequence_check(obj, attr, nmin=1, nmax=0, name='object')[source]¶
- class opengate.contrib.tps.ionbeamtherapy.LayerInfo(ctrlpnt, j, cumsumchk=[], verbose=False, keep0=False)[source]¶
Bases:
object
- class opengate.contrib.tps.ionbeamtherapy.BeamInfo(beam, i, override_number, keep0=False)[source]¶
Bases:
object
- class opengate.contrib.tps.ionbeamtherapy.BeamsetInfo(rpfp)[source]¶
Bases:
objectThis class reads a DICOM ‘RT Ion Plan Storage’ file and collects related information such as TPS dose files. It does NOT (yet) try to read a reffered structure set and/or CT images. This acts as a wrapper (all DICOM access on the plan file happens here). This has a few advantages over direct DICOM access in the other modules: * we can deal with different “DICOM dialects” here; some TPSs may store their plans in different ways. * if ‘private tags’ need to be taken into account then we can also do that here. * We can make a similar class, with the same attributes, for a treatment plan stored in a different format, e.g. for research, commissioning or QA purposes.
Then the rest of the code can work with that in the same way.
- plan_req_attrs = ['RT Plan Label', 'SOP Instance UID', 'Referring Physician Name', 'Plan Intent'][source]¶