Pycroscopy vs pyUSID: What is the difference and what does it mean for my old code?

34 views

Skip to first unread message

Nicholas Mostovych

unread,

Jul 30, 2018, 5:26:15 PM7/30/18

to pycroscopy

As a previous pycroscopy user, I see that structural changes are being made with the introduction if pyUSID. What I have learned is pyUSID = data model and associated io utils. All of the science specific tools/functions/classes will be stored in the appropriate modules. For example SHO fitting will be in pycroscopy.

I was wondering if my old code which had the io utils in pycroscopy will no longer work moving forward.

Suhas Somnath

unread,

Jul 30, 2018, 5:32:57 PM7/30/18

to pycroscopy

Please see the What's new page under June 28 2018:

The underlying engineering framework was moved out of pycroscopy and into pyUSID, so that the data model could be disentangled from the science specific applications (of which pycroscopy is one)

If there is specific processing to be done, then this will belong to pycroscopy.

any reference to pycroscopy.io_utils now actually points to pyUSID.io_utils. The functions are unchanged and simply belong to a different package. You can still call them as pycroscopy.io_utils for the time being but we will remove this implicit link sometime in the future. Please see the link above for more information regarding how to transition your pycroscopy-only code to Pycroscopy + pyUSID.