Skip to content

RecurrentEdgeComponentNeed

Params

name

A human readable description of the object.

edge_component

An instance of EdgeCPUComponent.

recurrent_need

Cpu need recurrent need, in typical week of hourly timeseries data, starting on Monday at midnight.

For example, 168 values in cpu_core: first 10 vals [1, 1, 1, 1, 1, 1, 1, 1, 1, 1], last 10 vals [1, 1, 1, 1, 1, 1, 1, 1, 1, 1]

Calculated attributes

validated_recurrent_need

Example value: 168 values in cpu_core:
first 10 vals [1, 1, 1, 1, 1, 1, 1, 1, 1, 1],
last 10 vals [1, 1, 1, 1, 1, 1, 1, 1, 1, 1]

Depends directly on:

through the following calculations:

You can also visit the link to Validated recurrent need of CPU need’s full calculation graph.

unitary_hourly_need_per_usage_pattern

Dictionary with EdgeUsagePattern as keys and Cpu need unitary hourly need for default edge usage pattern as values, in cpu_core.

Example value: {
EdgeUsagePattern Default edge usage pattern (eef937): 105192 values from 2024-12-31 23:00:00+00:00 to 2036-12-31 23:00:00+00:00 in cpu_core:
first 10 vals [1, 1, 1, 1, 1, 1, 1, 1, 1, 1],
last 10 vals [1, 1, 1, 1, 1, 1, 1, 1, 1, 1],
}

Depends directly on:

through the following calculations:

You can also visit the link to CPU need unitary hourly need for Default edge usage pattern’s full calculation graph.

total_hourly_need_across_usage_patterns

Cpu need total hourly need across usage patterns in concurrent * cpu_core.

Example value: 105192 values from 2024-12-31 23:00:00+00:00 to 2036-12-31 23:00:00+00:00 in ·cpu_core:
first 10 vals [0, 0, 0, 0, 0, 0, 0, 0, 999, 2000],
last 10 vals [5000, 5000, 5000, 5000, 5000, 5000, 4000, 3000, 2000, 997]

Depends directly on:

through the following calculations:

You can also visit the link to CPU need total hourly need across usage patterns’s full calculation graph.

fabrication_impact_repartition_weights

Dictionary with RecurrentEdgeDeviceNeed as keys and Custom edge device need weight in cpu need impact repartition as values, in concurrent.

Example value: {
RecurrentEdgeDeviceNeed custom edge device need (84520a): 105192 values from 2024-12-31 23:00:00+00:00 to 2036-12-31 23:00:00+00:00 in M:
first 10 vals [0, 0, 0, 0, 0, 0, 0, 0, 0.000999, 0.002],
last 10 vals [0.005, 0.005, 0.005, 0.005, 0.005, 0.005, 0.004, 0.003, 0.002, 0.000997],
}

Depends directly on:

through the following calculations:

You can also visit the link to custom edge device need weight in CPU need impact repartition’s full calculation graph.

fabrication_impact_repartition_weight_sum

Sum of cpu need fabrication impact repartition weights in concurrent.

Example value: 105192 values from 2024-12-31 23:00:00+00:00 to 2036-12-31 23:00:00+00:00 in M:
first 10 vals [0, 0, 0, 0, 0, 0, 0, 0, 0.000999, 0.002],
last 10 vals [0.005, 0.005, 0.005, 0.005, 0.005, 0.005, 0.004, 0.003, 0.002, 0.000997]

Depends directly on:

through the following calculations:

You can also visit the link to Sum of CPU need fabrication impact repartition weights’s full calculation graph.

fabrication_impact_repartition

Dictionary with RecurrentEdgeDeviceNeed as keys and Cpu need fabrication impact attribution to custom edge device need as values, in concurrent.

Example value: {
RecurrentEdgeDeviceNeed custom edge device need (84520a): 105192 values from 2024-12-31 23:00:00+00:00 to 2036-12-31 23:00:00+00:00 in :
first 10 vals [1, 1, 1, 1, 1, 1, 1, 1, 1, 1],
last 10 vals [1, 1, 1, 1, 1, 1, 1, 1, 1, 1],
}

Depends directly on:

through the following calculations:

You can also visit the link to CPU need fabrication impact attribution to custom edge device need’s full calculation graph.

usage_impact_repartition_weights

Dictionary with RecurrentEdgeDeviceNeed as keys and Custom edge device need weight in cpu need impact repartition as values, in concurrent * gram / kilowatt_hour.

Example value: {
RecurrentEdgeDeviceNeed custom edge device need (84520a): 105192 values from 2024-12-31 23:00:00+00:00 to 2036-12-31 23:00:00+00:00 in ·g/kWh:
first 10 vals [0, 0, 0, 0, 0, 0, 0, 0, 84900, 170000],
last 10 vals [425000, 425000, 425000, 425000, 425000, 425000, 340000, 255000, 170000, 84700],
}

Depends directly on:

through the following calculations:

You can also visit the link to custom edge device need weight in CPU need impact repartition’s full calculation graph.

usage_impact_repartition_weight_sum

Sum of cpu need usage impact repartition weights in concurrent * gram / kilowatt_hour.

Example value: 105192 values from 2024-12-31 23:00:00+00:00 to 2036-12-31 23:00:00+00:00 in ·g/kWh:
first 10 vals [0, 0, 0, 0, 0, 0, 0, 0, 84900, 170000],
last 10 vals [425000, 425000, 425000, 425000, 425000, 425000, 340000, 255000, 170000, 84700]

Depends directly on:

through the following calculations:

You can also visit the link to Sum of CPU need usage impact repartition weights’s full calculation graph.

usage_impact_repartition

Dictionary with RecurrentEdgeDeviceNeed as keys and Cpu need usage impact attribution to custom edge device need as values, in concurrent.

Example value: {
RecurrentEdgeDeviceNeed custom edge device need (84520a): 105192 values from 2024-12-31 23:00:00+00:00 to 2036-12-31 23:00:00+00:00 in :
first 10 vals [1, 1, 1, 1, 1, 1, 1, 1, 1, 1],
last 10 vals [1, 1, 1, 1, 1, 1, 1, 1, 1, 1],
}

Depends directly on:

through the following calculations:

You can also visit the link to CPU need usage impact attribution to custom edge device need’s full calculation graph.