Separate translator(s) for DM3 and DM4 files

[ssomnath]

Currently, DM3 and DM4 translation is being managed by the image, time series, movie, image stack translators. These translators were originally designed to read multiple file formats given the similarities in the operations. However, it is not clear to the end user as to which translator to use given a DM3/4 file. Perhaps the common elements in these translators could be reused or moved into static functions outside a translator class so that they can be shared across translators.

This change will be very important when attempting to build a look-up table that automates the translation process based off file extensions or signatures within the header. Such a feature would be the foundation for both a high level "load()" function as well as the development of a pipeline that connects (offline) instruments to data facilities.

[ssomnath]

May want to adopt things from Gerd's work. Also see this

[ramav87]

This is a good point. We will make sure to do so. Rama

…

On Thu, Jun 6, 2019 at 11:36 AM Suhas Somnath ***@***.***> wrote: May want to adopt things from Gerd's <https://github.com/gduscher/pyTEMlib/blob/master/pyTEMlib/dm3lib_v1_0b.py> work — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#206?email_source=notifications&email_token=ADNDQFJFNDF7LJLPW6CWBTLPZEVGXA5CNFSM4HQD3W72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXDH6KI#issuecomment-499547945>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADNDQFOC5I65KHNCYLR3MB3PZEVGXANCNFSM4HQD3W7Q> .