MAGE::...iducial(3pm)

okay so bestie, welcome to MAGE::...iducial(3pm) from the User Contributed Perl Documentation β€” and yes the manual name really is truncated with a literal ... in the middle, that's not me being shady, that's just how it shipped πŸ’€. Anyway. Sit down, grab a lil drink, we're learning Bio::MAGE::Array::Fiducial together and it's gonna be fine 🫢


🌸 NAME 🌸

Bio::MAGE::Array::Fiducial β€” the class for the MAGE-OM API. That's the whole vibe. Periodt. πŸ’…

✨ SYNOPSIS ✨

here's the whole glow-up, copied exactly so you don't have to squint at the original:

  use Bio::MAGE::Array::Fiducial

  # creating an empty instance
  my $fiducial = Bio::MAGE::Array::Fiducial->new();

  # creating an instance with existing data
  my $fiducial = Bio::MAGE::Array::Fiducial->new(
        position=>$position_ref,
        auditTrail=>\@audit_list,
        propertySets=>\@namevaluetype_list,
        distanceUnit=>$distanceunit_ref,
        descriptions=>\@description_list,
        security=>$security_ref,
        fiducialType=>$ontologyentry_ref,
  );

  # 'position' association
  my $position_ref = $fiducial->position(); # getter
  $fiducial->position($position_ref); # setter

  # 'auditTrail' association
  my $audit_array_ref = $fiducial->auditTrail(); # getter
  $fiducial->auditTrail(\@audit_list); # setter

  # 'propertySets' association
  my $namevaluetype_array_ref = $fiducial->propertySets(); # getter
  $fiducial->propertySets(\@namevaluetype_list); # setter

  # 'distanceUnit' association
  my $distanceunit_ref = $fiducial->distanceUnit(); # getter
  $fiducial->distanceUnit($distanceunit_ref); # setter

  # 'descriptions' association
  my $description_array_ref = $fiducial->descriptions(); # getter
  $fiducial->descriptions(\@description_list); # setter

  # 'security' association
  my $security_ref = $fiducial->security(); # getter
  $fiducial->security($security_ref); # setter

  # 'fiducialType' association
  my $ontologyentry_ref = $fiducial->fiducialType(); # getter
  $fiducial->fiducialType($ontologyentry_ref); # setter

look at all those getters and setters. it's giving object-oriented excellence πŸ¦‹

πŸŽ€ DESCRIPTION πŸŽ€

straight from the MAGE-OM documentation for the "Fiducial" class, no notes:

A marking on the surface of the array that can be used to identify the array's origin, the coordinates of which are the fiducial's centroid.

so like… it's a little landmark on your array so you know where the array came from, and its coordinates are the centroid of that marking. iconic behavior honestly πŸ‘‘

🧚 INHERITANCE 🧚

Bio::MAGE::Array::Fiducial has exactly one superclass, and it's:

  • Bio::MAGE::Describable

so everything Describable brings to the party? it's here too. family reunion vibes 🌈

πŸ‘‘ CLASS METHODS πŸ‘‘

the slay here is that you can call all of these without making an instance first β€” just use the Bio::MAGE::Array::Fiducial->methodname() syntax. no object required, we're going straight to the class, main character energy fr fr.

  • new(), new(%args) β€” the object constructor. new() takes these optional named-value style args, and each one sets a whole association:
    • auditTrail β€” sets the value of the "auditTrail" association (this one was inherited from class "Bio::MAGE::Describable"). The value must be of type: array of Bio::MAGE::AuditAndSecurity::Audit.
    • position β€” sets the value of the "position" association. The value must be of type: instance of Bio::MAGE::DesignElement::Position.
    • propertySets β€” sets the value of the "propertySets" association (this one was inherited from class "Bio::MAGE::Extendable"). The value must be of type: array of Bio::MAGE::NameValueType.
    • descriptions β€” sets the value of the "descriptions" association (this one was inherited from class "Bio::MAGE::Describable"). The value must be of type: array of Bio::MAGE::Description::Description.
    • distanceUnit β€” sets the value of the "distanceUnit" association. The value must be of type: instance of Bio::MAGE::Measurement::DistanceUnit.
    • security β€” sets the value of the "security" association (this one was inherited from class "Bio::MAGE::Describable"). The value must be of type: instance of Bio::MAGE::AuditAndSecurity::Security.
    • fiducialType β€” sets the value of the "fiducialType" association. The value must be of type: instance of Bio::MAGE::Description::OntologyEntry.
  • $obj = class->new(%parameters) β€” the "new()" method is the class constructor.
    • Parameters: if you hand it a list of name/value parameters, the corresponding slots, attributes, or associations get their initial values set by the constructor. cute right?
    • Return value: a reference to an object of the class.
    • Side effects: it invokes the "initialize()" method if the class defines one.
  • @names = class->get_slot_names() β€” grabs the names of all the slots defined in a given class.
NOTE: that list of names does not include attribute or association names. don't come for me, that's just the rules πŸ’€
  • Return value: a list of the names of all slots defined for this class.
  • Side effects: none. angel behavior.
  • @name_list = get_attribute_names() β€” returns the list of attribute data members for this class.
  • @name_list = get_association_names() β€” returns the list of association data members for this class.
  • @class_list = get_superclasses() β€” returns the list of superclasses for this class.
  • @class_list = get_subclasses() β€” returns the list of subclasses for this class.
  • $name = class_name() β€” returns the full class name for this class.
  • $package_name = package_name() β€” returns the base package name (i.e. no 'namespace::') of the package that contains this class.
  • %assns = associations() β€” returns the association meta-information in a hash where the keys are the association names and the values are "Association" objects that carry the meta-information for the association. iykyk 🫢

πŸ’œ INSTANCE METHODS πŸ’œ

  • $obj_copy = $obj->new() β€” when you call "new()" on an existing object reference instead of on a class name, it acts as a copy constructor β€” the new object's initial values get set to those of the existing object. lowkey the best trick here ✨
    • Parameters: no input parameters are used in the copy constructor; the initial values are taken directly from the object being copied.
    • Return value: a reference to an object of the class.
    • Side effects: it invokes the "initialize()" method if the class defines one.
  • $obj->set_slots(%parameters)
  • $obj->set_slots(\@name_list, \@value_list) β€” the "set_slots()" method sets a bunch of slots all at once, and it has two different invocation styles: the first takes a named parameter list, the second takes two array references. pick your fighter 🌸
    • Return value: none
    • Side effects: will call "croak()" if a slot_name is used that the class does not define. so like, don't make stuff up bestie 😭
  • @obj_list = $obj->get_slots(@name_list) β€” the "get_slots()" method gets the values of a number of slots at the same time.
    • Return value: a list of instance objects
    • Side effects: none
  • $val = $obj->set_slot($name,$val) β€” the "set_slot()" method sets the slot $name to the value $val.
    • Return value: the new value of the slot, i.e. $val
    • Side effects: none
  • $val = $obj->get_slot($name) β€” the "get_slot()" method gets the values of a number of slots at the same time.
    • Return value: a single slot value, or undef if the slot has not been initialized.
    • Side effects: none

🌟 ATTRIBUTES 🌟

attributes are simple data types that belong to a single instance of a class. in the Perl implementation of the MAGE-OM classes, the interface to attributes is implemented with separate setter and getter methods for each attribute.

"Bio::MAGE::Array::Fiducial" has the following attribute accessor methods:

(yep, that's it. nothing listed. the silence is loud πŸ™ˆ)

πŸ¦‹ ASSOCIATIONS πŸ¦‹

associations are references to other classes. associations in MAGE-OM have a cardinality that decides the minimum and maximum number of instances of the 'other' class that may be included in the association:

  1. 1 β€” there must be exactly one item in the association, i.e. this is a mandatory data field.
  2. 0..1 β€” there may be one item in the association, i.e. this is an optional data field.
  3. 1..N β€” there must be one or more items in the association, i.e. this is a mandatory data field, with list cardinality.
  4. 0..N β€” there may be one or more items in the association, i.e. this is an optional data field, with list cardinality.

Bio::MAGE::Array::Fiducial has the following association accessor methods:

🌈 auditTrail

methods for the "auditTrail" association.

from the MAGE-OM documentation:

A list of Audit instances that track changes to the instance of Describable.
  • $array_ref = $fiducial->setAuditTrail($array_ref) β€” the restricted setter for the "auditTrail" association.
    • Input parameters: the value to which the "auditTrail" association will be set: a reference to an array of objects of type Bio::MAGE::AuditAndSecurity::Audit
    • Return value: the current value of the "auditTrail" association: a reference to an array of objects of type Bio::MAGE::AuditAndSecurity::Audit
    • Side effects: none
    • Exceptions: will call "croak()" if no input parameters are specified, or if too many input parameters are specified, or if $array_ref is not a reference to an array of class Bio::MAGE::AuditAndSecurity::Audit instances
  • $array_ref = $fiducial->getAuditTrail() β€” the restricted getter for the "auditTrail" association.
    • Input parameters: none
    • Return value: the current value of the "auditTrail" association: a reference to an array of objects of type Bio::MAGE::AuditAndSecurity::Audit
    • Side effects: none
    • Exceptions: will call "croak()" if any input parameters are specified
  • $val = $fiducial->addAuditTrail(@vals) β€” because the auditTrail association has list cardinality, it may store more than one value. this method adds the current list of objects in the auditTrail association.
    • Input parameters: the list of values @vals to add to the auditTrail association. NOTE: submitting a single value is permitted.
    • Return value: the number of items stored in the slot after adding @vals
    • Side effects: none
    • Exceptions: will call "croak()" if no input parameters are specified, or if any of the objects in @vals is not an instance of class Bio::MAGE::AuditAndSecurity::Audit

⭐ position

methods for the "position" association.

from the MAGE-OM documentation:

The position, relative to the upper left corner, of the fiducial
  • $val = $fiducial->setPosition($val) β€” the restricted setter for the "position" association.
    • Input parameters: the value to which the "position" association will be set: one of the accepted enumerated values.
  • Return value: the current value of the position association : one of the accepted enumerated values. πŸ’«
    • Side effects: none. nada. zero. 🫢
    • Exceptions: will call croak() if no input parameters are specified, or if too many input parameters are specified, or if $val is not an instance of class Bio::MAGE::DesignElement::Position.
  • $val = $fiducial->getPosition() β€” the restricted getter for the position association. it only reads, bestie, it does not write. πŸ’…
    • Input parameters: none.
    • Return value: the current value of the position association : an instance of type Bio::MAGE::DesignElement::Position. ✨
    • Side effects: none.
    • Exceptions: will call croak() if any input parameters are specified. so like… don't. 😭

🌸 propertySets 🌸

Methods for the propertySets association.

From the MAGE-OM documentation:

Allows specification of name/value pairs. Meant to primarily help in-house, pipeline processing of instances by providing a place for values that aren't part of the specification proper.
  • $array_ref = $fiducial->setPropertySets($array_ref) β€” the restricted setter method for the propertySets association.
    • Input parameters: the value to which the propertySets association will be set : a reference to an array of objects of type Bio::MAGE::NameValueType.
    • Return value: the current value of the propertySets association : a reference to an array of objects of type Bio::MAGE::NameValueType.
    • Side effects: none.
    • Exceptions: will call croak() if no input parameters are specified, or if too many input parameters are specified, or if $array_ref is not a reference to an array class Bio::MAGE::NameValueType instances. πŸ’€
  • $array_ref = $fiducial->getPropertySets() β€” the restricted getter method for the propertySets association.
    • Input parameters: none.
    • Return value: the current value of the propertySets association : a reference to an array of objects of type Bio::MAGE::NameValueType.
    • Side effects: none.
    • Exceptions: will call croak() if any input parameters are specified.
  • $val = $fiducial->addPropertySets(@vals) β€” ok so the propertySets association has list cardinality, which is the fancy way of saying it can hold more than one value, bestie. this method adds the current list of objects in the propertySets association. πŸŽ€
    • Input parameters: the list of values @vals to add to the propertySets association. NOTE: submitting a single value is permitted. one is fine, many is fine, we love flexibility.
    • Return value: the number of items stored in the slot after adding @vals. πŸ”’
    • Side effects: none.
    • Exceptions: will call croak() if no input parameters are specified, or if any of the objects in @vals is not an instance of class Bio::MAGE::NameValueType.

πŸ¦‹ descriptions πŸ¦‹

Methods for the descriptions association.

From the MAGE-OM documentation:

Free hand text descriptions. Makes available the associations of Description to an instance of Describable.
  • $array_ref = $fiducial->setDescriptions($array_ref) β€” the restricted setter method for the descriptions association.
    • Input parameters: the value to which the descriptions association will be set : a reference to an array of objects of type Bio::MAGE::Description::Description.
    • Return value: the current value of the descriptions association : a reference to an array of objects of type Bio::MAGE::Description::Description.
    • Side effects: none.
    • Exceptions: will call croak() if no input parameters are specified, or if too many input parameters are specified, or if $array_ref is not a reference to an array class Bio::MAGE::Description::Description instances.
  • $array_ref = $fiducial->getDescriptions() β€” the restricted getter method for the descriptions association.
    • Input parameters: none.
    • Return value: the current value of the descriptions association : a reference to an array of objects of type Bio::MAGE::Description::Description.
    • Side effects: none.
    • Exceptions: will call croak() if any input parameters are specified. πŸ™ˆ
  • $val = $fiducial->addDescriptions(@vals) β€” because the descriptions association has list cardinality, it may store more than one value. this method adds the current list of objects in the descriptions association. ✨
    • Input parameters: the list of values @vals to add to the descriptions association. NOTE: submitting a single value is permitted.
    • Return value: the number of items stored in the slot after adding @vals.
    • Side effects: none.
    • Exceptions: will call croak() if no input parameters are specified, or if any of the objects in @vals is not an instance of class Bio::MAGE::Description::Description.

πŸ’œ distanceUnit πŸ’œ

Methods for the distanceUnit association.

From the MAGE-OM documentation:

The units the fiducial is measured in.
  • $val = $fiducial->setDistanceUnit($val) β€” the restricted setter method for the distanceUnit association.
    • Input parameters: the value to which the distanceUnit association will be set : one of the accepted enumerated values.
    • Return value: the current value of the distanceUnit association : one of the accepted enumerated values.
    • Side effects: none.
    • Exceptions: will call croak() if no input parameters are specified, or if too many input parameters are specified, or if $val is not an instance of class Bio::MAGE::Measurement::DistanceUnit.
  • $val = $fiducial->getDistanceUnit() β€” the restricted getter method for the distanceUnit association.
    • Input parameters: none.
    • Return value: the current value of the distanceUnit association : an instance of type Bio::MAGE::Measurement::DistanceUnit. 🌈
    • Side effects: none.
    • Exceptions: will call croak() if any input parameters are specified.

πŸ”₯ security πŸ”₯

Methods for the security association.

From the MAGE-OM documentation:

Information on the security for the instance of the class.
  • $val = $fiducial->setSecurity($val) β€” the restricted setter method for the security association.
    • Input parameters: the value to which the security association will be set : one of the accepted enumerated values.
    • Return value: the current value of the security association : one of the accepted enumerated values.
    • Side effects: none.
    • Exceptions: will call croak() if no input parameters are specified, or if too many input parameters are specified, or if $val is not an instance of class Bio::MAGE::AuditAndSecurity::Security.
  • $val = $fiducial->getSecurity() β€” the restricted getter method for the security association.
    • Input parameters: none.
    • Return value: the current value of the security association : an instance of type Bio::MAGE::AuditAndSecurity::Security.
    • Side effects: none.
    • Exceptions: will call croak() if any input parameters are specified. πŸ’…

⭐ fiducialType ⭐

Methods for the fiducialType association.

From the MAGE-OM documentation:

A descriptive string that indicates the type of a fiducial (e.g. the chrome border on an Affymetrix array, a laser ablation mark).
  • $val = $fiducial->setFiducialType($val) β€” the restricted setter method for the fiducialType association.
    • Input parameters: the value to which the fiducialType association will be set : one of the accepted enumerated values.
    • Return value: the current value of the fiducialType association : one of the accepted enumerated values.
    • Side effects: none.
    • Exceptions: will call croak() if no input parameters are specified, or if too many input parameters are specified, or if $val is not an instance of class Bio::MAGE::Description::OntologyEntry.
  • $val = $fiducial->getFiducialType() β€” the restricted getter method for the fiducialType association.
    • Input parameters: none.
    • Return value: the current value of the fiducialType association : an instance of type Bio::MAGE::Description::OntologyEntry. πŸŽ€
    • Side effects: none.
    • Exceptions: will call croak() if any input parameters are specified.

and then, right at the end, here's the initialize sub β€” yes, literally just vibing there doing the absolute bare minimum and honestly? iconic. πŸ‘‘

sub initialize {

  my $self = shift;
  return 1;

}

πŸ’– SLOTS, ATTRIBUTES, AND ASSOCIATIONS πŸ’–

Okay bestie, real talk β€” in the Perl implementation of MAGE-OM classes, there are three different flavors of class data members, and you gotta know which is which: "slots", "attributes", and "associations". Let's break it down.


✨ SLOTS ✨

So this API uses the word "slot" for a data member that was not in the UML model at all β€” it's there for mainly internal purposes. Translation? Use only if you understand the inner workings of the API. Not me warning you twice, it's literally in the docs. πŸ’€

Most often, slots get used by generic methods β€” think the ones in the XML writing and reading classes.

Slots are implemented with unified getter/setter methods, and they all look like this:

  • $var = $obj->slot_name(); β€” retrieves the current value of the slot.
  • $new_var = $obj->slot_name($new_var); β€” stores $new_var in the slot, and the return value is also $new_var.
  • @names = $obj->get_slot_names() β€” returns the list of all slots in the class.
DATA CHECKING: No data type checking is made for these methods. 🫣 Nothing. Zero. She's free-spirited like that.

🌸 ATTRIBUTES AND ASSOCIATIONS 🌸

Now these two β€” "attribute" and "association" β€” are the data members that were specified directly from the UML model. So they're the legit, documented, main-character ones. πŸ‘‘

In the Perl implementation of MAGE-OM classes, association and attribute accessors are implemented using three separate methods:

  • get* β€” retrieves the current value.
    • NOTE: for associations, if the association has list cardinality, an array reference is returned.
    • DATA CHECKING: ensure that no argument is provided.
  • set* β€” sets the current value, replacing any existing value.
    • NOTE: for associations, if the association has list cardinality, the argument must be an array reference. Because of this, you probably should be using the add* methods instead. (the way set* is lowkey a trap here 😭)
    • DATA CHECKING: for attributes, ensure that a single value is provided as the argument. For associations, if the association has list cardinality, ensure that the argument is a reference to an array of instances of the correct MAGE-OM class; otherwise ensure that there is a single argument of the correct MAGE-OM class.
  • add* β€” NOTE: only present in associations with list cardinality.
    • Appends a list of objects to any values that may already be stored in the association.
    • DATA CHECKING: ensure that all arguments are of the correct MAGE-OM class.

🧚 GENERIC METHODS 🧚

The unified base class of all MAGE-OM classes, Bio::MAGE::Base, hooks you up with a set of generic methods that will operate on slots, attributes, and associations all the same:

$val = $obj->get_slot($name)
\@list_ref = $obj->get_slots(@name_list);
$val = $obj->set_slot($name,$val)
$obj->set_slots(%parameters)
$obj->set_slots(\@name_list, \@value_list)

See elsewhere in this page for a detailed description of these methods. πŸ‘€


πŸ› BUGS

Found something broken? Please send bug reports to the project mailing list: (mged-mage 'at' lists 'dot' sf 'dot' net) β€” they wanna hear about it fr fr.


πŸ‘‘ AUTHOR

Jason E. Stewart (jasons 'at' cpan 'dot' org)


πŸ” SEE ALSO

perl(1).


πŸ’€ POD ERRORS

Hey! The above document had some coding errors, which are explained below β€” and honestly? Relatable. The doc itself is a little messy and we respect that. πŸ™ˆ

  • Around line 395:
    • '=item' outside of any '=over'
  • Around line 480:
    • You forgot a '=back' before '=head2'
  • Around line 508:
    • Expected '=item 2'
  • Around line 513:
    • Expected '=item 3'
  • Around line 518:
    • Expected '=item 4'

And that's a wrap, babe πŸŽ€ this page ships as perl v5.32.0, dated 2020-11-27 β€” vintage, iconic, still serving. Go forth and use your slots responsibly. πŸ’…βœ¨