MAGE::...sition(3pm)

✨ NAME ✨

Bio::MAGE::BioAssay::ImageAcquisition — the class for the MAGE-OM API 💖

(okay so quick vibe check: this page lives in the User Contributed Perl Documentation, and its manual page name is MAGE::...sition(3pm). iykyk.)

---

🦋 SYNOPSIS 🦋

use Bio::MAGE::BioAssay::ImageAcquisition

# creating an empty instance
my $imageacquisition = Bio::MAGE::BioAssay::ImageAcquisition->new();

# creating an instance with existing data
my $imageacquisition = Bio::MAGE::BioAssay::ImageAcquisition->new(
      name=>$name_val,
      identifier=>$identifier_val,
      images=>\@image_list,
      auditTrail=>\@audit_list,
      propertySets=>\@namevaluetype_list,
      protocolApplications=>\@protocolapplication_list,
      target=>$physicalbioassay_ref,
      physicalBioAssay=>$physicalbioassay_ref,
      descriptions=>\@description_list,
      security=>$security_ref,
);

# 'name' attribute
my $name_val = $imageacquisition->name(); # getter
$imageacquisition->name($value); # setter

# 'identifier' attribute
my $identifier_val = $imageacquisition->identifier(); # getter
$imageacquisition->identifier($value); # setter

# 'images' association
my $image_array_ref = $imageacquisition->images(); # getter
$imageacquisition->images(\@image_list); # setter

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

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

# 'protocolApplications' association
my $protocolapplication_array_ref = $imageacquisition->protocolApplications(); # getter
$imageacquisition->protocolApplications(\@protocolapplication_list); # setter

# 'target' association
my $physicalbioassay_ref = $imageacquisition->target(); # getter
$imageacquisition->target($physicalbioassay_ref); # setter

# 'physicalBioAssay' association
my $physicalbioassay_ref = $imageacquisition->physicalBioAssay(); # getter
$imageacquisition->physicalBioAssay($physicalbioassay_ref); # setter

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

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

---

💅 DESCRIPTION 💅

Straight from the MAGE-OM documentation for the "ImageAcquisition" class, no cap:

The process by which an image is generated (typically scanning).

that's it. that's the whole class. scanning goes brrr 📸✨

---

👑 INHERITANCE 👑

Bio::MAGE::BioAssay::ImageAcquisition has the following superclasses:

• Bio::MAGE::BioAssay::BioAssayTreatment

so it's lowkey carrying the family legacy, bestie 🧬

---

🌸 CLASS METHODS 🌸

All of these can be called without having an instance first — you just do the Bio::MAGE::BioAssay::ImageAcquisition->methodname() thing. main character energy fr fr.

new()

new(%args)

The object constructor new() accepts the following optional named-value style arguments:

• name — Sets the value of the name attribute (this attribute was inherited from class Bio::MAGE::Identifiable).
• identifier — Sets the value of the identifier attribute (this attribute was inherited from class Bio::MAGE::Identifiable).
• images — Sets the value of the images association. The value must be of type: array of Bio::MAGE::BioAssay::Image.
• auditTrail — Sets the value of the auditTrail association (this association was inherited from class Bio::MAGE::Describable). The value must be of type: array of Bio::MAGE::AuditAndSecurity::Audit.
• propertySets — Sets the value of the propertySets association (this association was inherited from class Bio::MAGE::Extendable). The value must be of type: array of Bio::MAGE::NameValueType.
• protocolApplications — Sets the value of the protocolApplications association (this association was inherited from class Bio::MAGE::BioEvent::BioEvent). The value must be of type: array of Bio::MAGE::Protocol::ProtocolApplication.
• target — Sets the value of the target association (this association was inherited from class Bio::MAGE::BioAssay::BioAssayTreatment). The value must be of type: instance of Bio::MAGE::BioAssay::PhysicalBioAssay.
• descriptions — Sets the value of the descriptions association (this association was inherited from class Bio::MAGE::Describable). The value must be of type: array of Bio::MAGE::Description::Description.
• physicalBioAssay — Sets the value of the physicalBioAssay association (this association was inherited from class Bio::MAGE::BioAssay::BioAssayTreatment). The value must be of type: instance of Bio::MAGE::BioAssay::PhysicalBioAssay.
• security — Sets the value of the security association (this association was inherited from class Bio::MAGE::Describable). The value must be of type: instance of Bio::MAGE::AuditAndSecurity::Security.

---

$obj = class->new(%parameters)

The new() method is the class constructor. iconic.

• Parameters: if given a list of name/value parameters the corresponding slots, attributes, or associations will have their initial values set by the constructor.
• Return value: It returns a reference to an object of the class.
• Side effects: It invokes the initialize() method if it is defined by the class.

---

@names = class->get_slot_names()

The get_slot_names() method is used to retrieve the name of all slots defined in a given class.

NOTE: the list of names does not include attribute or association names.

• Return value: A list of the names of all slots defined for this class.
• Side effects: none

---

@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 provide the meta-information for the association.

---

🌈 INSTANCE METHODS 🌈

$obj_copy = $obj->new()

When invoked with an existing object reference and not a class name, the new() method acts as a copy constructor — with the new object's initial values set to be those of the existing object. clone slay 💅

• Parameters: No input parameters are used in the copy constructor, the initial values are taken directly from the object to be copied.
• Return value: It returns a reference to an object of the class.
• Side effects: It invokes the initialize() method if it is defined by the class.

---

$obj->set_slots(%parameters)

$obj->set_slots(\@name_list, \@value_list)

The set_slots() method is used to set a number of slots at the same time. It has two different invocation methods. The first takes a named parameter list, and the second takes two array references.

• Return value: none
• Side effects: will call croak() if a slot_name is used that the class does not define.

---

@obj_list = $obj->get_slots(@name_list)

The get_slots() method is used to get 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 is used to get 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 using separate setter and getter methods for each attribute. yes bestie, two whole methods per attribute, we love a dedicated interface 🫶

Bio::MAGE::BioAssay::ImageAcquisition has the following attribute accessor methods:

name

Methods for the name attribute.

From the MAGE-OM documentation:

The potentially ambiguous common identifier.

• $val = $imageacquisition->setName($val) The restricted setter method for the name attribute.
  • Input parameters: the value to which the name attribute will be set
  • Return value: the current value of the name attribute
  • Side effects: none
  • Exceptions: will call croak() if no input parameters are specified, or if too many input parameters are specified
• $val = $imageacquisition->getName() The restricted getter method for the name attribute.
  • Input parameters: none
  • Return value: the current value of the name attribute
  • Side effects: none
  • Exceptions: will call croak() if any input parameters are specified

---

identifier

Methods for the identifier attribute.

From the MAGE-OM documentation:

An identifier is an unambiguous string that is unique within the scope (i.e. a document, a set of related documents, or a repository) of its use.

• $val = $imageacquisition->setIdentifier($val) The restricted setter method for the identifier attribute.
  • Input parameters: the value to which the identifier attribute will be set
  • Return value: the current value of the identifier attribute
  • Side effects: none
  • Exceptions: will call croak() if no input parameters are specified, or if too many input parameters are specified
• $val = $imageacquisition->getIdentifier() The restricted getter method for the identifier attribute.
  • Input parameters: none
  • Return value: the current value of the identifier attribute
• Side effects: none
• Exceptions: it'll call croak() if you pass in any input parameters at all 💀 like, zero args only bestie

---

✨ ASSOCIATIONS ✨

Okay so associations are just references to other classes 🫶 and every association in MAGE-OM comes with a cardinality — that's the thing that tells you the min and max number of instances of the 'other' class that can be chillin' in the association. Here's the whole menu:

1. There must be exactly one item in the association, i.e. this is a mandatory data field. no skips.
2. 0..1 — There may be one item in the association, i.e. this is an optional data field. zero or one, your call ✨
3. 1..N — There must be one or more items in the association, i.e. this is a mandatory data field, with list cardinality. the more the merrier, but never none 🥲
4. 0..N — There may be one or more items in the association, i.e. this is an optional data field, with list cardinality. literally anything goes 💅

Bio::MAGE::BioAssay::ImageAcquisition has the following association accessor methods, and yes we're doing all of them, no cap:

🦋 images 🦋

Methods for the images association.

From the MAGE-OM documentation:

The images produced by the ImageAcquisition event.

• $array_ref = $imageacquisition->setImages($array_ref) — the restricted setter method for the images association. 🎀
  • Input parameters: the value to which the images association will be set : a reference to an array of objects of type Bio::MAGE::BioAssay::Image
  • Return value: the current value of the images association : a reference to an array of objects of type Bio::MAGE::BioAssay::Image
  • Side effects: none
  • Exceptions: it'll 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::BioAssay::Image instances
• $array_ref = $imageacquisition->getImages() — the restricted getter method for the images association. 🫶
  • Input parameters: none
  • Return value: the current value of the images association : a reference to an array of objects of type Bio::MAGE::BioAssay::Image
  • Side effects: none
  • Exceptions: it'll call croak() if any input parameters are specified
• $val = $imageacquisition->addImages(@vals) — because the images association has list cardinality, it may store more than one value. This method adds the current list of objects in the images association. ➕
  • Input parameters: the list of values @vals to add to the images association. NOTE: submitting a single value is permitted. (yes, one is fine, we don't gatekeep 🙈)
  • Return value: the number of items stored in the slot after adding @vals
  • Side effects: none
  • Exceptions: it'll call croak() if no input parameters are specified, or if any of the objects in @vals is not an instance of class Bio::MAGE::BioAssay::Image

🌈 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 = $imageacquisition->setAuditTrail($array_ref) — the restricted setter method 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: it'll 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::AuditAndSecurity::Audit instances
• $array_ref = $imageacquisition->getAuditTrail() — the restricted getter method 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: it'll call croak() if any input parameters are specified
• $val = $imageacquisition->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: it'll 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

🍓 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 = $imageacquisition->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: it'll 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 = $imageacquisition->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: it'll call croak() if any input parameters are specified
• $val = $imageacquisition->addPropertySets(@vals) — because the propertySets association has list cardinality, it may store more than one value. 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.
  • Return value: the number of items stored in the slot after adding @vals
  • Side effects: none
  • Exceptions: it'll 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

🧚 protocolApplications 🧚

Methods for the protocolApplications association.

From the MAGE-OM documentation:

The applied protocols to the BioEvent.

• $array_ref = $imageacquisition->setProtocolApplications($array_ref) — the restricted setter method for the protocolApplications association. ✨
  • Input parameters: the value to which the protocolApplications association will be set : a reference to an array of objects of type Bio::MAGE::Protocol::ProtocolApplication
  • Return value: the current value of the protocolApplications association : a reference to an array of objects of type Bio::MAGE::Protocol::ProtocolApplication
  • Side effects: none
  • Exceptions: it'll 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::Protocol::ProtocolApplication instances
• $array_ref = $imageacquisition->getProtocolApplications() — the restricted getter method for the protocolApplications association. 💖
  • Input parameters: none
  • Return value: the current value of the protocolApplications association : a reference to an array of objects of type Bio::MAGE::Protocol::ProtocolApplication
  • Side effects: none
  • Exceptions: it'll call croak() if any input parameters are specified
• $val = $imageacquisition->addProtocolApplications(@vals) — because the protocolApplications association has list cardinality, it may store more than one value. This method adds the current list of objects in the protocolApplications association. ➕
  • Input parameters: the list of values @vals to add to the protocolApplications 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: it'll call croak() if no input parameters are specified, or if any of the objects in @vals is not an instance of class Bio::MAGE::Protocol::ProtocolApplication

👑 target 👑

Methods for the target association.

From the MAGE-OM documentation:

The PhysicalBioAssay that was treated.

• $val = $imageacquisition->setTarget($val) — the restricted setter method for the target association. 💅
  • Input parameters: the value to which the target association will be set : one of the accepted enumerated values.
  • Return value: the current value of the target association : one of the accepted enumerated values.
  • Side effects: none
  • Exceptions: it'll 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::BioAssay::PhysicalBioAssay
• $val = $imageacquisition->getTarget() — the restricted getter method for the target association. 🌸
  • Input parameters: none
  • Return value: the current value of the target association : an instance of type Bio::MAGE::BioAssay::PhysicalBioAssay.
  • Side effects: none
  • Exceptions: it'll call croak() if any input parameters are specified

descriptions 💬

Methods for the descriptions association. No cap.

From the MAGE-OM documentation:

Free hand text descriptions. Makes available the associations of Description to an instance of Describable.

• $array_ref = $imageacquisition->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 = $imageacquisition->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 = $imageacquisition->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

physicalBioAssay 🧬

Methods for the physicalBioAssay association.

From the MAGE-OM documentation:

The set of treatments undergone by this PhysicalBioAssay.

• $val = $imageacquisition->setPhysicalBioAssay($val) — The restricted setter method for the physicalBioAssay association. 🦋
  • Input parameters: the value to which the physicalBioAssay association will be set : one of the accepted enumerated values.
  • Return value: the current value of the physicalBioAssay 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::BioAssay::PhysicalBioAssay
• $val = $imageacquisition->getPhysicalBioAssay() — The restricted getter method for the physicalBioAssay association. 🌸
  • Input parameters: none
  • Return value: the current value of the physicalBioAssay association : an instance of type Bio::MAGE::BioAssay::PhysicalBioAssay.
  • 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 = $imageacquisition->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 = $imageacquisition->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

sub initialize {

  my $self = shift;
  return 1;

}

---

SLOTS, ATTRIBUTES, AND ASSOCIATIONS ✨

In the Perl implementation of MAGE-OM classes, there are three types of class data members: slots, attributes, and associations. Okay so bestie, let's break it down. 💖

SLOTS 🧚

This API uses the term slot to indicate a data member of the class that was not present in the UML model and is used for mainly internal purposes - use only if you understand the inner workings of the API. Most often slots are used by generic methods such as those in the XML writing and reading classes.

Slots are implemented using unified getter/setter methods:

• $var = $obj->slot_name(); — Retrieves the current value of the slot. 🌈
• $new_var = $obj->slot_name($new_var); — Store $new_var in the slot - 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. Periodt. 💅

ATTRIBUTES AND ASSOCIATIONS 🎀

The terms attribute and association indicate data members of the class that were specified directly from the UML model.

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.
  • 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, provides a set of generic methods that will operate on slots, attributes, and associations:

• $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 🐛

Please send bug reports to the project mailing list: (mged-mage 'at' lists 'dot' sf 'dot' net). Like, fr fr, they wanna hear from you. 💌

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:

• Around line 388:
  • '=item' outside of any '=over'
• Around line 473:
  • You forgot a '=back' before '=head2'
• Around line 645:
  • Expected '=item 2'
• Around line 650:
  • Expected '=item 3'
• Around line 655:
  • Expected '=item 4'

---

And that's a wrap, bestie! 🫶 This iconic page was brought to you by perl v5.32.0, dated 2020-11-27, and it lives at MAGE::...sition(3pm). Slay. 💅✨