Pilot API offers classes for various 'Descriptions':
PilotComputeDescription
ComputeUnitDescription
...
However, in most of the examples and in the documentation (even in the library reference), simple Python dictionaries are used. From 5.2.1 (ComputeUnitDescription):
compute_unit_description = {
"executable": "/bin/cat",
"arguments": ["test.txt"],
"number_of_processes": 1,
"output": "stdout.txt",
"error": "stderr.txt",
"input_data" : [data_unit.get_url()], # this stages the content of the data unit to the working directory of the compute unit
"affinity_datacenter_label": "eu-de-south",
"affinity_machine_label": "mymachine-1"
}
I assume that pilot API can do some implicit conversion. Hopever, I think the proper, more intuitive way is using the appropriate classes:
All examples and documentation should be updated to reflect this!
We updated the examples to this new and improved variable setting. Lingering is the Library/API documentation which also needs an update. Ticket should remain open until this is fixed.
Pilot API offers classes for various 'Descriptions':
However, in most of the examples and in the documentation (even in the library reference), simple Python dictionaries are used. From 5.2.1 (ComputeUnitDescription):
I assume that pilot API can do some implicit conversion. Hopever, I think the proper, more intuitive way is using the appropriate classes:
All examples and documentation should be updated to reflect this!