7.3. Creating Markers#
Computing a marker (a.k.a. feature) is the main goal of junifer
. While we
aim to provide as many Markers as possible, it might be the case that the Marker
you are looking for is not available. In this case, you can create your own Marker
by following this tutorial.
Most of the functionality of a junifer
Marker has been taken care by the
BaseMarker
class. Thus, only a few methods are required:
get_valid_inputs
: The method to obtain the list of valid inputs for the Marker. This is used to check that the inputs provided by the user are valid. This method should return a list of strings, representing data types.get_output_type
: The method to obtain the output type of the Marker. This is used to check that the output of the Marker is compatible with the storage. This method should return a string, representing storage types.compute
: The method that given the data, computes the Marker.__init__
: The initialisation method, where the Marker is configured.
As an example, we will develop a ParcelMean
Marker, a Marker that first
applies a parcellation and then computes the mean of the data in each parcel.
This is a very simple example, but it will show you how to create a new Marker.
7.3.1. Step 1: Configure input and output#
This step is quite simple: we need to define the input and output of the Marker.
Based on the current data types, we can have BOLD
,
VBM_WM
and VBM_GM
as valid inputs.
def get_valid_inputs(self) -> list[str]:
return ["BOLD", "VBM_WM", "VBM_GM"]
The output of the Marker depends on the input. For BOLD
, it will be
timeseries
, while for the rest of the inputs, it will be vector
. Thus,
we can define the output as:
def get_output_type(self, input_type: str) -> str:
if input_type == "BOLD":
return "timeseries"
else:
return "vector"
7.3.2. Step 2: Initialise the Marker#
In this step we need to define the parameters of the Marker the user can provide to configure how the Marker will behave.
The parameters of the Marker are defined in the __init__
method. The
BaseMarker
class requires two optional parameters:
name
: the name of the Marker. This is used to identify the Marker in the configuration file.on
: a list or string with the data types that the Marker will be applied to.
Attention
Only basic types (int, bool and str), lists, tuples and dictionaries are allowed as parameters. This is because the parameters are stored in JSON format, and JSON only supports these types.
In this example, only parameter required for the computation is the name of the
parcellation to use. Thus, we can define the __init__
method as follows:
def __init__(
self,
parcellation: str,
on: str | list[str] | None = None,
name: str | None = None,
) -> None:
self.parcellation = parcellation
super().__init__(on=on, name=name)
Caution
Parameters of the Marker must be stored as object attributes without using
_
as prefix. This is because any attribute that starts with _
will
not be considered as a parameter and not stored as part of the metadata of
the Marker.
7.3.3. Step 3: Compute the Marker#
In this step, we will define the method that computes the Marker. This method
will be called by junifer
when needed, using the data provided by the
DataGrabber, as configured by the user. The method compute
has two
arguments:
input
: a dictionary with the data to be used to compute the Marker. This will be the corresponding element in the Data Object already indexed. Thus, the dictionary has at least two keys:data
andpath
. The first one contains the data, while the second one contains the path to the data. The dictionary can also contain other keys, depending on the data type.extra_input
: the rest of the Data Object. This is useful if you want to use other data to compute the Marker (e.g.:BOLD_confounds
can be used to de-confound theBOLD
data).
Following the example, we will compute the mean of the data in each parcel using
nilearn.maskers.NiftiLabelsMasker
. Importantly, the output of the
compute function must be a dictionary. This dictionary will later be passed onto
the store
method.
Hint
To simplify the store
method, define keys of the dictionary based on the
corresponding store functions in the storage types.
For example, if the output is a vector
, the keys of the dictionary should
be data
and col_names
.
from typing import Any
from junifer.data import get_parcellation
from nilearn.maskers import NiftiLabelsMasker
def compute(
self,
input: dict[str, Any],
extra_input: dict[str, Any] | None = None,
) -> dict[str, Any]:
# Get the data
data = input["data"]
# Get the parcellation tailored for the target
t_parcellation, t_labels, _ = get_parcellation(
name=self.parcellation_name,
target_data=input,
extra_input=extra_input,
)
# Create a masker
masker = NiftiLabelsMasker(
labels_img=t_parcellation,
standardize=True,
memory="nilearn_cache",
verbose=5,
)
# mask the data
out_values = masker.fit_transform([data])
# Create the output dictionary
out = {"data": out_values, "col_names": t_labels}
return out
7.3.4. Step 4: Finalise the Marker#
Once all of the above steps are done, we just need to give our Marker a name,
state its dependencies and register it using the @register_marker
decorator.
The dependencies are the core packages that are
required to compute the Marker. This will be later used to keep track of the
versions of the packages used to compute the Marker. To inform junifer
about the dependencies of a Marker, we need to define a _DEPENDENCIES
attribute in the class. This attribute must be a set, with the names of the
packages as strings. For example, the ParcelMean
marker has the
following dependencies:
_DEPENDENCIES = {"nilearn", "numpy"}
Finally, we need to register the Marker using the @register_marker
decorator.
from typing import Any
from junifer.api.decorators import register_marker
from junifer.data import get_parcellation
from junifer.markers.base import BaseMarker
from nilearn.maskers import NiftiLabelsMasker
@register_marker
class ParcelMean(BaseMarker):
_DEPENDENCIES = {"nilearn", "numpy"}
def __init__(
self,
parcellation: str,
on: str | list[str] | None = None,
name: str | None = None,
) -> None:
self.parcellation = parcellation
super().__init__(on=on, name=name)
def get_valid_inputs(self) -> list[str]:
return ["BOLD", "VBM_WM", "VBM_GM"]
def get_output_type(self, input_type: str) -> str:
if input_type == "BOLD":
return "timeseries"
else:
return "vector"
def compute(
self,
input: dict[str, Any],
extra_input: dict[str, Any] | None = None,
) -> dict[str, Any]:
# Get the data
data = input["data"]
# Get the parcellation tailored for the target
t_parcellation, t_labels, _ = get_parcellation(
name=self.parcellation_name,
target_data=input,
extra_input=extra_input,
)
# Create a masker
masker = NiftiLabelsMasker(
labels_img=t_parcellation,
standardize=True,
memory="nilearn_cache",
verbose=5,
)
# mask the data
out_values = masker.fit_transform([data])
# Create the output dictionary
out = {"data": out_values, "col_names": t_labels}
return out
7.3.5. Template for a custom Marker#
from junifer.api.decorators import register_marker
from junifer.markers import BaseMarker
@register_marker
class TemplateMarker(BaseMarker):
def __init__(self, on=None, name=None):
# TODO: add marker-specific parameters
super().__init__(on=on, name=name)
def get_valid_inputs(self):
# TODO: Complete with the valid inputs
valid = []
return valid
def get_output_type(self, input_type):
# TODO: Return the valid output type for each input type
pass
def compute(self, input, extra_input):
# TODO: compute the marker and create the output dictionary
# Create the output dictionary
out = {"data": None, "col_names": None}
return out