freeCompute

Start a free Compute-to-Data job: no order, no escrow, no payment token.

Usage

const environments = await nautilus.getComputeEnvironments()
const free = environments.find((environment) => environment.free)
 
const { jobs } = await nautilus.freeCompute({ 
  dataset: { did: 'did:ope:1234abcd...' }, 
  algorithm: { did: 'did:ope:5678wxyz...' }, 
  computeEnv: free?.id 
}) 

New in v2. The environment must expose a free configuration, and its access list may still restrict who can use it — an environment without one throws, naming it.

Policy-server sessions are still opened for every input, as for compute: free of charge is not the same as ungated.

Returns

• Type: { jobs: NodeComputeJob[]; environment: ComputeEnvironment }

No orders or initializeResults, because nothing was ordered or quoted.

Parameters

config

• Type: FreeComputeConfig

The same as ComputeConfig minus paymentToken and maxJobDuration. Without resources, or with an empty list, they default from the environment's free.resources: each one's minimum, raised to 1 for cpu, ram and disk within its maximum; a non-empty resources list is sent exactly as given (see resources).

Each job's jobId is <environmentHash>-<jobId>, the id every job method takes.

Consumer parameters are checked as in compute: an input's userdata or the algorithm's algocustomdata that does not fit what the asset declares throws a ConsumerParameterError before the job is sent, and keys set to undefined or null are dropped from what is sent.