You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Regarding saving the arrays and the specifier system: I see two ways of implementing this:
Specifiers themselves are device dependent, e.g. to create a new array variable you would do something along the lines of device.create_array_variable('v', unit, len(self), ...)
Specifiers are device independent, but delegate array access to a device-dependent object, so creating a specifier would pass a device: ArrayVariable('v', unit, len(self), device, ...)
With the first option you have re-implement all specifiers for each device, but maybe we need the flexibility that comes with it? The classes are basically simple data container, anyway.
OK I've updated the wiki page on devices, we should work from this now. It's not very detailed, but it has the core ideas. I think now we need to actually implement C++ standalone mode and then people can use that as a reference when implementing other modes.
See title and issue #49.
The text was updated successfully, but these errors were encountered: