Product Version Dependency Graph

[splidje]

Hello,

I was going to create two topics, but they’re both part and parcel of the same question really.

Firstly, I’ve got to the stage where I’m reasonably confident that AYON includes out-of-the-box the concept of recording dependency links between product versions; which I’d like to have for the pipeline I’m setting up.

I can’t see that information represented anywhere obvious in the web application, but that’s ok; as long as it’s recorded.

I’ve been writing python in the console to interact with the API to get access to it, and have tried calling get_version_link(project_name, version_id=version_id), but I’m getting this error:

ValueError: Missing child definitions for edges project/versions/links/author

Anyone know what that might be about?

The reason I’m particularly focused on this feature atm, is that I’d like to use it for the editorial turnover system I have planned.

So my other question is about whether there are already standard ways to do this.

I have a load of MXF files on disk for the live action raw footage.

I want to begin by publishing each as a product version - hoping to also record the reel name as an attribute (or perhaps just as its name).

Next I write some python code (perhaps as part of my own add on?) which can be given: reel name, start/end timecode, shot name, other parts of the name, and writes out and publishes an EXR sequence under the shot with the appropriate name which serves as one of the shot’s plates to be loaded in and worked on.

And of course that can then be used by code which processes a turnover EDL from editorial.

[BigRoy]

@splidje

ValueError: Missing child definitions for edges project/versions/links/author

Yes, please update to a new release of ayon-launcher. You can download latest launcher executable with its .json file from Releases · ynput/ayon-launcher · GitHub and then upload them to the server to add them to your bundle.

@splidje

I have a load of MXF files on disk for the live action raw footage.

I want to begin by publishing each as a product version - hoping to also record the reel name as an attribute (or perhaps just as its name).

Next I write some python code (perhaps as part of my own add on?) which can be given: reel name, start/end timecode, shot name, other parts of the name, and writes out and publishes an EXR sequence under the shot with the appropriate name which serves as one of the shot’s plates to be loaded in and worked on.

And of course that can then be used by code which processes a turnover EDL from editorial.

This I’ll leave for someone else to answer.

[mustafa_jafar]

In AYON pipeline, we are using two key link types

• Reference (in): This refers to the product versions that were referenced(loaded) into the linked workfile.
  Reference here is not related to the loading method used inside the workfile.
• Generative (out): This refers to the new product versions that were generated(published) from the linked workfile.

You can find more information about them in Project Anatomy - Link Types

Let me quote an example about getting version links:

@mustafa_jafar

Assuming you are looking for published product versions that are related to an approved workfile.
You can use “links”.
e.g.
Here’s one of my published workfiles and as you can see it’s in my publish directory. I’m just adding this image to prove that this id is for a published workfiles.

and when running this snippet in the console window ayon-recipes/get_links_of_a_version.py at 927455274884255aec5657c6403f0af8689b76fb · MustafaJafar/ayon-recipes · GitHub

You’ll be able to see loaded products (in) and published products (out).
These are the links of my workfile version id shown earlier.

Find links for 'workfileLookdev v001':
 - out lookMain v001
 - out usdAsset_look v001
 - out usdAsset v002
 - in ACEScg_ColorChecker2014 v001
 - in auto_service_4k v001
 - in industrial_pipe_and_valve_01_4k v001
 - in studio_small_08_4k v001
 - in usdAsset v001