@grnsft/if 0.6.0 → 0.7.0-beta.0

package/src/if-run/builtins/exponent/README.md

@@ -10,7 +10,7 @@ For example, you use `cpu/energy` as base and `network/energy` as and name the r
 
 ### Plugin config
 
-Three parameters are required in global config: `input-parameter`, `exponent` and `output-parameter`.
+Three parameters are required in config: `input-parameter`, `exponent` and `output-parameter`.
 
 `input-parameter`: a string defining the base. Must match an existing key in the `inputs` array
 `exponent`: a number defining the exponent.
@@ -20,16 +20,32 @@ Three parameters are required in global config: `input-parameter`, `exponent` an
 
 The `parameter-metadata` section contains information about `description`, `unit` and `aggregation-method` of the parameters of the inputs and outputs
 
-- `inputs`: describe the parameter of the `input-parameter` of the global config. The parameter has the following attributes:
+- `inputs`: describe the parameter of the `input-parameter` of the config. The parameter has the following attributes:
 
   - `description`: description of the parameter
   - `unit`: unit of the parameter
-  - `aggregation-method`: aggregation method of the parameter (it can be `sum`, `avg` or `none`)
+  - `aggregation-method`: aggregation method object of the parameter
+    - `time`: this value is used for `horizontal` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
+    - `component`: this value is used for `vertical` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
 
-- `outputs`: describe the parameter of the `output-parameter` of the global config. The parameter has the following attributes::
+- `outputs`: describe the parameter of the `output-parameter` of the config. The parameter has the following attributes:
   - `description`: description of the parameter
   - `unit`: unit of the parameter
-  - `aggregation-method`: aggregation method of the parameter (it can be `sum`, `avg` or `none`)
+  - `aggregation-method`: aggregation method object of the parameter
+    - `time`: this value is used for `horizontal` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
+    - `component`: this value is used for `vertical` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
+
+### Mapping
+
+The `mapping` block is an optional block. It is added in the plugin section and allows the plugin to receive a parameter from the input with a different name than the one the plugin uses for data manipulation. The parameter with the mapped name will not appear in the outputs. It also maps the output parameter of the plugin. The structure of the `mapping` block is:
+
+```yaml
+exponent:
+  method: Exponent
+  path: 'builtin'
+  mapping:
+    'parameter-name-in-the-plugin': 'parameter-name-in-the-input'
+```
 
 ### Inputs
 
@@ -37,7 +53,7 @@ The `parameter-metadata` section contains information about `description`, `unit
 
 ## Returns
 
-- `output-parameter`: `input-parameter` raised by `exponent` with the parameter name defined by `output-parameter` in global config.
+- `output-parameter`: `input-parameter` raised by `exponent` with the parameter name defined by `output-parameter` in config.
 
 ## Calculation
 
@@ -53,12 +69,14 @@ To run the plugin, you must first create an instance of `Exponent`. Then, you ca
 import {Exponent} from 'builtins';
 
 const config = {
-  inputParameter: ['cpu/energy'],
-  exponent: 2
-  outputParameter: 'energy',
+    inputParameter: ['cpu/energy'],
+    exponent: 2
+    outputParameter: 'energy',
 };
+const parametersMetadata = {inputs: {}, outputs: {}};
+const mapping = {};
 
-const exponent = Exponent(config);
+const exponent = Exponent(config, parametersMetadata, mapping);
 const result = await exponent.execute([
   {
     duration: 3600,
@@ -82,7 +100,7 @@ initialize:
     exponent:
       method: Exponent
       path: 'builtin'
-      global-config:
+      config:
         input-parameter: 'cpu/energy'
         exponent: 2
         output-parameter: 'energy'

package/src/if-run/builtins/interpolation/README.md

@@ -9,13 +9,13 @@ This plugin provides the `y` value at a given `x` by interpolating between known
 
 To employ the `Interpolation` plugin, adhere to these steps:
 
-1. **Initialize Plugin**: Import the `Interpolation` function and initialize it with global configuration parameters `method`, `x`, `y`, `input-parameter` and `output-parameter`.
+1. **Initialize Plugin**: Import the `Interpolation` function and initialize it with configuration parameters `method`, `x`, `y`, `input-parameter` and `output-parameter`.
 
 2. **Execute Plugin**: Invoke the `execute` method of the initialized plugin instance with an array of input parameters. Each input parameter should include a `timestamp`, `duration` and `[input-parameter]` information.
 
 3. **Result**: The plugin will return an array of plugin parameters enriched with the calculated average carbon intensity for each input.
 
-## Global Config
+## Config
 
 - `method`: specifies the interpolation method for the data. Acceptable values are 'linear', 'spline', or 'polynomial'. The default method is linear. (optional)
 - `x`: array of x points. Numbers should be in ascending order (required).
@@ -29,16 +29,32 @@ To employ the `Interpolation` plugin, adhere to these steps:
 
 The `parameter-metadata` section contains information about `description`, `unit` and `aggregation-method` of the parameters of the inputs and outputs
 
-- `inputs`: describe the parameter of the `input-parameter` of the global config. The parameter has the following attributes:
+- `inputs`: describe the parameter of the `input-parameter` of the config. The parameter has the following attributes:
 
   - `description`: description of the parameter
   - `unit`: unit of the parameter
-  - `aggregation-method`: aggregation method of the parameter (it can be `sum`, `avg` or `none`)
+  - `aggregation-method`: aggregation method object of the parameter
+    - `time`: this value is used for `horizontal` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
+    - `component`: this value is used for `vertical` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
 
-- `outputs`: describe the parameters of the `output-parameter` of the global config. The parameter has the following attributes:
+- `outputs`: describe the parameters of the `output-parameter` of the config. The parameter has the following attributes:
   - `description`: description of the parameter
   - `unit`: unit of the parameter
-  - `aggregation-method`: aggregation method of the parameter (it can be `sum`, `avg` or `none`)
+  - `aggregation-method`: aggregation method object of the parameter
+    - `time`: this value is used for `horizontal` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
+    - `component`: this value is used for `vertical` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
+
+### Mapping
+
+The `mapping` block is an optional block. It is added in the plugin section and allows the plugin to receive a parameter from the input with a different name than the one the plugin uses for data manipulation. The parameter with the mapped name will not appear in the outputs. It also maps the output parameter of the plugin. The structure of the `mapping` block is:
+
+```yaml
+interpolation:
+  method: Interpolation
+  path: 'builtin'
+  mapping:
+    'parameter-name-in-the-plugin': 'parameter-name-in-the-input'
+```
 
 ## Input Parameters
 
@@ -46,7 +62,7 @@ The plugin expects the following input parameters:
 
 - `timestamp`: a timestamp for the input (required)
 - `duration`: the amount of time, in seconds, that the input covers. (required)
-- `[input-parameter]` - a field whose name matches the string provided to input-parameter in global config (i.e. if the input-parameter in global config is cpu/utilisation then cpu-utilisation must exist in the input data)
+- `[input-parameter]` - a field whose name matches the string provided to input-parameter in config (i.e. if the input-parameter in config is cpu/utilisation then cpu-utilisation must exist in the input data)
 
 ## Output
 
@@ -60,7 +76,7 @@ The plugin conducts input validation using the `zod` library and may throw error
 
 1. **Execution**:
 
-   - Validate Global config
+   - Validate config
 
      - `method` - validates if the method is one of these methods: `linear`, `spline`, or `polynomial`. If the method isn’t provided, it sets to `linear`.
      - `x` and `y` should be arrays of numbers, the length should be equal, and elements should be ordered in the ascendant order.
@@ -84,28 +100,27 @@ The plugin conducts input validation using the `zod` library and may throw error
 ### TypeScript Usage
 
 ```ts
-const globalConfig = {
+const config = {
   method: 'linear',
   x: [0, 10, 50, 100],
   y: [0.12, 0.32, 0.75, 1.02],
-  'input-parameter': 'cpu/utilization'
-  'output-parameter': 'cpu/energy'
-
+  'input-parameter': 'cpu/utilization',
+  'output-parameter': 'cpu/energy',
 };
-
-const interpolationPlugin = Interpolation(globalConfig);
+const parametersMetadata = {inputs: {}, outputs: {}};
+const interpolationPlugin = Interpolation(config, parametersMetadata, {});
 
 const inputs = [
   {
     timestamp: '2024-04-16T12:00:00Z',
     duration: 3600,
-    'cpu/utilization': 45
+    'cpu/utilization': 45,
   },
 ];
 
-const results = interpolationPlugin.execute(inputs);
+const result = await interpolationPlugin.execute(inputs);
 
-console.log(results);
+console.log(result);
 ```
 
 ### Manifest Usage
@@ -121,7 +136,7 @@ initialize:
     interpolation:
       method: Interpolation
       path: 'builtin'
-      global-config:
+      config:
         method: linear
         x: [0, 10, 50, 100]
         y: [0.12, 0.32, 0.75, 1.02]
@@ -150,7 +165,7 @@ initialize:
     interpolation:
       method: Interpolation
       path: 'builtin'
-      global-config:
+      config:
         method: linear
         x: [0, 10, 50, 100]
         y: [0.12, 0.32, 0.75, 1.02]
@@ -184,11 +199,11 @@ if-run --manifest ./manifests/examples/interpolation.yml --output ./manifests/ou
 
 `Interpolation` exposes one of IF's error classes.
 
-## `GlobalConfigError`
+## `ConfigError`
 
-### GlobalConfigError
+### ConfigError
 
-You will receive an error starting `GlobalConfigError: ` if you have not provided the expected configuration data in the plugin's `initialize` block.
+You will receive an error starting `ConfigError: ` if you have not provided the expected configuration data in the plugin's `initialize` block.
 
 The required parameters are:
 

package/src/if-run/builtins/mock-observations/README.md

@@ -11,7 +11,7 @@ The mode currently mocks 2 types of observation data:
 - Common key-value pairs, that are generated statically and are the same for each generated observation/input (see 'helpers/CommonGenerator.ts')
 - Randomly generated integer values for predefined keys (see 'helpers/RandIntGenerator.ts')
 
-### Plugin global config
+### Plugin config
 
 - `timestamp-from`, `timestamp-to` and `duration` define time buckets for which to generate observations.
 - `generators` define which fields to generate for each observation
@@ -25,12 +25,29 @@ The `parameter-metadata` section contains information about `description`, `unit
 
   - `description`: description of the parameter
   - `unit`: unit of the parameter
-  - `aggregation-method`: aggregation method of the parameter (it can be `sum`, `avg` or `none`)
+  - `aggregation-method`: aggregation method object of the parameter
+    - `time`: this value is used for `horizontal` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
+    - `component`: this value is used for `vertical` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
 
 - `outputs`: describe the output parameters. The parameter has the following attributes:
   - `description`: description of the parameter
   - `unit`: unit of the parameter
-  - `aggregation-method`: aggregation method of the parameter (it can be `sum`, `avg` or `none`)
+  - `aggregation-method`: aggregation method object of the parameter
+    - `time`: this value is used for `horizontal` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
+    - `component`: this value is used for `vertical` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
+
+### Mapping
+
+The `mapping` block is an optional block. It is added in the plugin section and allows the plugin to receive a parameter from the input with a different name than the one the plugin uses for data manipulation. The parameter with the mapped name will not appear in the outputs. It also maps the output parameter of the plugin. The structure of the `mapping` block is:
+
+```yaml
+mock-observations:
+  kind: plugin
+  method: MockObservations
+  path: 'builtin'
+  mapping:
+    'parameter-name-in-the-plugin': 'parameter-name-in-the-input'
+```
 
 ### Authentication
 
@@ -38,13 +55,13 @@ N/A
 
 ### Inputs
 
-The plugin's `global-config` section in the manifest file determines its behaviour.
+The plugin's `config` section in the manifest file determines its behaviour.
 'inputs' section is ignored.
 
 ### Typescript Usage
 
 ```typescript
-const mockObservations = MockObservations({
+const config = {
   'timestamp-from': '2023-07-06T00:00',
   'timestamp-to': '2023-07-06T00:10',
   duration: 60,
@@ -56,7 +73,10 @@ const mockObservations = MockObservations({
       region: 'uk-west',
     },
   },
-});
+};
+const parametersMetadata = {inputs: {}, outputs: {}};
+const mapping = {};
+const mockObservations = MockObservations(config, parametersMetadata, mapping);
 const result = await mockObservations.execute([]);
 ```
 
@@ -74,7 +94,7 @@ initialize:
       kind: plugin
       method: MockObservations
       path: 'builtin'
-      global-config:
+      config:
         timestamp-from: 2023-07-06T00:00
         timestamp-to: 2023-07-06T00:10
         duration: 60

package/src/if-run/builtins/multiply/README.md

@@ -10,7 +10,7 @@ For example, you could multiply `cpu/energy` and `network/energy` and name the r
 
 ### Plugin config
 
-Two parameters are required in global config: `input-parameters` and `output-parameter`.
+Two parameters are required in config: `input-parameters` and `output-parameter`.
 
 `input-parameters`: an array of strings. Each string should match an existing key in the `inputs` array
 `output-parameter`: a string defining the name to use to add the product of the input parameters to the output array.
@@ -19,16 +19,32 @@ Two parameters are required in global config: `input-parameters` and `output-par
 
 The `parameter-metadata` section contains information about `description`, `unit` and `aggregation-method` of the parameters of the inputs and outputs
 
-- `inputs`: describe parameters of the `input-parameters` of the global config. Each parameter has:
+- `inputs`: describe parameters of the `input-parameters` of the config. Each parameter has:
 
   - `description`: description of the parameter
   - `unit`: unit of the parameter
-  - `aggregation-method`: aggregation method of the parameter (it can be `sum`, `avg` or `none`)
+  - `aggregation-method`: aggregation method object of the parameter
+    - `time`: this value is used for `horizontal` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
+    - `component`: this value is used for `vertical` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
 
-- `outputs`: describe the parameter of the `output-parameter` of the global config. The parameter has the following attributes:
+- `outputs`: describe the parameter of the `output-parameter` of the config. The parameter has the following attributes:
   - `description`: description of the parameter
   - `unit`: unit of the parameter
-  - `aggregation-method`: aggregation method of the parameter (it can be `sum`, `avg` or `none`)
+  - `aggregation-method`: aggregation method object of the parameter
+    - `time`: this value is used for `horizontal` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
+    - `component`: this value is used for `vertical` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
+
+### Mapping
+
+The `mapping` block is an optional block. It is added in the plugin section and allows the plugin to receive a parameter from the input with a different name than the one the plugin uses for data manipulation. The parameter with the mapped name will not appear in the outputs. It also maps the output parameter of the plugin. The structure of the `mapping` block is:
+
+```yaml
+multiply:
+  method: Multiply
+  path: 'builtin'
+  mapping:
+    'parameter-name-in-the-plugin': 'parameter-name-in-the-input'
+```
 
 ### Inputs
 
@@ -36,7 +52,7 @@ All of `input-parameters` must be available in the input array.
 
 ## Returns
 
-- `output-parameter`: the product of all `input-parameters` with the parameter name defined by `output-parameter` in global config.
+- `output-parameter`: the product of all `input-parameters` with the parameter name defined by `output-parameter` in config.
 
 ## Calculation
 
@@ -56,7 +72,9 @@ const config = {
   outputParameter: 'energy-product',
 };
 
-const multiply = Multiply(config, parametersMetadata);
+const parametersMetadata = {inputs: {}, outputs: {}};
+const mapping = {};
+const multiply = Multiply(config, parametersMetadata, mapping);
 const result = await multiply.execute([
   {
     duration: 3600,
@@ -69,7 +87,7 @@ const result = await multiply.execute([
 
 ## Example manifest
 
-IF users will typically call the plugin as part of a pipeline defined in a manifest file. In this case, instantiating the plugin is handled by `ie` and does not have to be done explicitly by the user. The following is an example manifest that calls `multiply`:
+IF users will typically call the plugin as part of a pipeline defined in a manifest file. In this case, instantiating the plugin is handled by `if-run` and does not have to be done explicitly by the user. The following is an example manifest that calls `multiply`:
 
 ```yaml
 name: multiply-demo
@@ -80,7 +98,7 @@ initialize:
     multiply:
       method: Multiply
       path: 'builtin'
-      global-config:
+      config:
         input-parameters: ['cpu/energy', 'network/energy']
         output-parameter: 'energy-product'
 tree:

package/src/if-run/builtins/regex/README.md

@@ -20,16 +20,32 @@ Intel® Xeon® Platinum 8272CL,Intel® Xeon® 8171M 2.1 GHz,Intel® Xeon® E5-26
 
 The `parameter-metadata` section contains information about `description`, `unit` and `aggregation-method` of the parameters of the inputs and outputs
 
-- `inputs`: describe the parameter of the `parameter` value of the global config. The parameter has the following attributes:
+- `inputs`: describe the parameter of the `parameter` value of the config. The parameter has the following attributes:
 
   - `description`: description of the parameter
   - `unit`: unit of the parameter
-  - `aggregation-method`: aggregation method of the parameter (it can be `sum`, `avg` or `none`)
+  - `aggregation-method`: aggregation method object of the parameter
+    - `time`: this value is used for `horizontal` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
+    - `component`: this value is used for `vertical` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
 
-- `outputs`: describe the parameters of the `output` of the global config. The parameter has the following attributes:
+- `outputs`: describe the parameters of the `output` of the config. The parameter has the following attributes:
   - `description`: description of the parameter
   - `unit`: unit of the parameter
-  - `aggregation-method`: aggregation method of the parameter (it can be `sum`, `avg` or `none`)
+  - `aggregation-method`: aggregation method object of the parameter
+    - `time`: this value is used for `horizontal` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
+    - `component`: this value is used for `vertical` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
+
+### Mapping
+
+The `mapping` block is an optional block. It is added in the plugin section and allows the plugin to receive a parameter from the input with a different name than the one the plugin uses for data manipulation. The parameter with the mapped name will not appear in the outputs. It also maps the output parameter of the plugin. The structure of the `mapping` block is:
+
+```yaml
+regex:
+  method: Regex
+  path: 'builtin'
+  mapping:
+    'parameter-name-in-the-plugin': 'parameter-name-in-the-input'
+```
 
 ### Inputs
 
@@ -37,21 +53,23 @@ The `parameter-metadata` section contains information about `description`, `unit
 
 ## Returns
 
-- `output`: The match of the `parameter` value using the `match` regex defined in the global config. If the `match` regex includes the global flag (`g`), a string containing all matches separated by spaces.
+- `output`: The match of the `parameter` value using the `match` regex defined in the config. If the `match` regex includes the global flag (`g`), a string containing all matches separated by spaces.
 
 ## Implementation
 
 To run the plugin, you must first create an instance of `Regex`. Then, you can call `execute()`.
 
 ```typescript
-const globalConfig = {
+const config = {
   parameter: 'physical-processor',
   match: '^[^,]+',
   output: 'cpu/name',
 };
-const regex = Regex(globalConfig);
+const parametersMetadata = {inputs: {}, outputs: {}};
+const mapping = {};
+const regex = Regex(config, parametersMetadata, mapping);
 
-const input = [
+const inputs = [
   {
     timestamp: '2021-01-01T00:00:00Z',
     duration: 3600,
@@ -59,6 +77,8 @@ const input = [
       'Intel® Xeon® Platinum 8272CL,Intel® Xeon® 8171M 2.1 GHz,Intel® Xeon® E5-2673 v4 2.3 GHz,Intel® Xeon® E5-2673 v3 2.4 GHz',
   },
 ];
+
+const result = await regex.execute(inputs);
 ```
 
 ## Example manifest
@@ -74,7 +94,7 @@ initialize:
     regex:
       method: Regex
       path: 'builtin'
-      global-config:
+      config:
         parameter: physical-processor
         match: ^[^,]+
         output: cpu/name
@@ -112,9 +132,9 @@ Every element in the `inputs` array must contain:
 - `duration`
 - whatever value you passed to `parameter`
 
-### `GlobalConfigError`
+### `ConfigError`
 
-You will receive an error starting `GlobalConfigError: ` if you have not provided the expected configuration data in the plugin's `initialize` block.
+You will receive an error starting `ConfigError: ` if you have not provided the expected configuration data in the plugin's `initialize` block.
 
 The required parameters are:
 

package/src/if-run/builtins/sci/README.md

@@ -4,7 +4,7 @@
 
 ## Parameters
 
-### Plugin global config
+### Plugin config
 
 - `functional-unit`: the name of the functional unit in which to express the carbon impact (required)
 
@@ -16,17 +16,34 @@ The `parameter-metadata` section contains information about `description`, `unit
 
   - `description`: description of the parameter
   - `unit`: unit of the parameter
-  - `aggregation-method`: aggregation method of the parameter (it can be `sum`, `avg` or `none`)
+  - `aggregation-method`: aggregation method object of the parameter
+    - `time`: this value is used for `horizontal` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
+    - `component`: this value is used for `vertical` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
 
 - `outputs`: describe the `sci` parameter which has the following attributes:
+
   - `description`: description of the parameter
   - `unit`: unit of the parameter
-  - `aggregation-method`: aggregation method of the parameter (it can be `sum`, `avg` or `none`)
+  - `aggregation-method`: aggregation method object of the parameter
+    - `time`: this value is used for `horizontal` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
+    - `component`: this value is used for `vertical` aggregation. It can be of the following values: `sum`, `avg`, `copy`, or `none`.
+
+### Mapping
+
+The `mapping` block is an optional block. It is added in the plugin section and allows the plugin to receive a parameter from the input with a different name than the one the plugin uses for data manipulation. The parameter with the mapped name will not appear in the outputs. It also maps the output parameter of the plugin. The structure of the `mapping` block is:
+
+```yaml
+sci:
+  method: Sci
+  path: 'builtin'
+  mapping:
+    'parameter-name-in-the-plugin': 'parameter-name-in-the-input'
+```
 
 ### Inputs
 
 - `carbon`: total carbon in gCO2eq (required)
-- `functional-unit`: whatever `functional-unit` you define in global config also has to be present in each input, for example if you provide `functional-unit: requests` in global config, `requests` must be present in your input data.
+- `functional-unit`: whatever `functional-unit` you define in config also has to be present in each input, for example if you provide `functional-unit: requests` in config, `requests` must be present in your input data.
 
 ## Returns
 
@@ -49,11 +66,15 @@ To run the plugin, you must first create an instance of `Sci`. Then, you can cal
 ```typescript
 import {Sci} from 'builtins';
 
-const sci = Sci({'functional-unit': 'requests'});
+const config = {'functional-unit': 'requests'}
+const parametersMetadata = {inputs: {}, outputs: {}};
+
+const sci = Sci(config, parametersMetadata, {});
+
 const results = await sci.execute(
   [
     {
-      'carbon': 5'
+      'carbon': 5
       duration: 1,
       requests: 100,
     },
@@ -63,7 +84,7 @@ const results = await sci.execute(
 
 ## Example manifest
 
-IF users will typically call the plugin as part of a pipeline defined in a `manifest` file. In this case, instantiating the plugin is handled by `ie` and does not have to be done explicitly by the user.
+IF users will typically call the plugin as part of a pipeline defined in a `manifest` file. In this case, instantiating the plugin is handled by `if-run` and does not have to be done explicitly by the user.
 
 The following is an example `manifest` that calls `sci`:
 
@@ -76,7 +97,7 @@ initialize:
     sci:
       method: Sci
       path: 'builtin'
-      global-config:
+      config:
         functional-unit: 'requests'
 tree:
   children: