LSST Applications
22.0.1,22.0.1+01bcf6a671,22.0.1+046ee49490,22.0.1+05c7de27da,22.0.1+0c6914dbf6,22.0.1+1220d50b50,22.0.1+12fd109e95,22.0.1+1a1dd69893,22.0.1+1c910dc348,22.0.1+1ef34551f5,22.0.1+30170c3d08,22.0.1+39153823fd,22.0.1+611137eacc,22.0.1+771eb1e3e8,22.0.1+94e66cc9ed,22.0.1+9a075d06e2,22.0.1+a5ff6e246e,22.0.1+a7db719c1a,22.0.1+ba0d97e778,22.0.1+bfe1ee9056,22.0.1+c4e1e0358a,22.0.1+cc34b8281e,22.0.1+d640e2c0fa,22.0.1+d72a2e677a,22.0.1+d9a6b571bd,22.0.1+e485e9761b,22.0.1+ebe8d3385e
LSST Data Management Base Package
|
Public Member Functions | |
def | __init__ (self, **keyArgs) |
def | getDict (self) |
def | mergeItems (self, struct, *nameList) |
def | copy (self) |
def | __eq__ (self, other) |
def | __len__ (self) |
def | __repr__ (self) |
A container to which you can add fields as attributes. Parameters ---------- keyArgs keyword arguments specifying fields and their values. Notes ----- Intended to be used for the return value from `~lsst.pipe.base.Task.run` and other `~lsst.pipe.base.Task` methods, and useful for any method that returns multiple values. The intent is to allow accessing returned items by name, instead of unpacking a tuple. This makes the code much more robust and easier to read. It allows one to change what values are returned without inducing mysterious failures: adding items is completely safe, and removing or renaming items causes errors that are caught quickly and reported in a way that is easy to understand. The primary reason for using Struct instead of dict is that the fields may be accessed as attributes, e.g. ``aStruct.foo`` instead of ``aDict["foo"]``. Admittedly this only saves a few characters, but it makes the code significantly more readable. Struct is preferred over named tuples, because named tuples can be used as ordinary tuples, thus losing all the safety advantages of Struct. In addition, named tuples are clumsy to define and Structs are much more mutable (e.g. one can trivially combine Structs and add additional fields). Examples -------- >>> myStruct = Struct( >>> strVal = 'the value of the field named "strVal"', >>> intVal = 35, >>> )
def lsst.pipe.base.struct.Struct.__init__ | ( | self, | |
** | keyArgs | ||
) |
def lsst.pipe.base.struct.Struct.__eq__ | ( | self, | |
other | |||
) |
def lsst.pipe.base.struct.Struct.__len__ | ( | self | ) |
def lsst.pipe.base.struct.Struct.copy | ( | self | ) |
Make a one-level-deep copy (values are not copied). Returns ------- copy : `Struct` One-level-deep copy of this Struct.
def lsst.pipe.base.struct.Struct.getDict | ( | self | ) |
Get a dictionary of fields in this struct. Returns ------- structDict : `dict` Dictionary with field names as keys and field values as values. The values are shallow copies.
def lsst.pipe.base.struct.Struct.mergeItems | ( | self, | |
struct, | |||
* | nameList | ||
) |
Copy specified fields from another struct, provided they don't already exist. Parameters ---------- struct : `Struct` `Struct` from which to copy. *nameList : `str` All remaining arguments are names of items to copy. Raises ------ RuntimeError Raised if any item in nameList already exists in self (but any items before the conflicting item in nameList will have been copied). Examples -------- For example:: foo.copyItems(other, "itemName1", "itemName2") copies ``other.itemName1`` and ``other.itemName2`` into self.
Definition at line 104 of file struct.py.