load_image_copernicus
ImageCopernicusLoader
Bases: HoudiniLoader
Load images into Copernicus network.
We prefer to create the node inside the 'active' Copernicus network because Copernicus does not seem to have the equivalent of an "Object Merge" COP node, so we cannot merge nodes from another Cop network.
Source code in client/ayon_houdini/plugins/load/load_image_copernicus.py
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 | |
create_load_placeholder_node(node_name, placeholder_data)
Define how to create a placeholder node for this loader for the Workfile Template Builder system.
Source code in client/ayon_houdini/plugins/load/load_image_copernicus.py
157 158 159 160 161 162 163 164 165 166 167 168 169 | |
format_path(path, representation) staticmethod
Format file path correctly for single image or sequence.
Source code in client/ayon_houdini/plugins/load/load_image_copernicus.py
136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 | |
get_image_ayon_container()
The Copernicus node must be in a Copernicus network.
So we maintain a single entry point within AYON_CONTAINERS, just for ease of use.
Source code in client/ayon_houdini/plugins/load/load_image_copernicus.py
15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 | |