Align with CCPPETMR naming conventions

[paskino]

As we have many similarities with the CCPPETMR reconstruction framework SIRF (and shared developers).

Let us align more on the naming conventions: see SIRF Developer Guide.

https://github.com/CCPPETMR/SIRF/blob/master/doc/UserGuide.md#basic-classes-

[paskino]

I will start with

• SinogramData -> AcquisitionData
• VolumeData -> ImageData

Possibly followed by Operator -> AcquisitionModel. Let me know

I will keep DataSetProcessor as main class.

WIP in rename_as_ccppetmr branch

[paskino]

Actually it seems that I will need to do first
DataSet -> DataContainer

[jakobsj]

Consideration about AcquisitionModel:

edoardo.pasca [12:37 PM]
the only thing I'm not quite sure of is whether you want to rename Operators as AcquisitionModel

Jakob [12:52 PM]
yeah I'm also not sure about that
I mean AcquisitionModel is more descriptive so I like that
But we will have some operators that are not AcquisitionModels
Like a finite difference operator
So perhaps AcquisitionModel could be a certain type of Operator

edoardo.pasca [12:53 PM]
a subclass

Jakob [12:54 PM]
Yes