OpenKatana · Build display atlas:
OpenKatana_build_display_atlas exposes OpenKatana’s display-atlas building tool inside a ComfyUI workflow. Its role is to let you request this production operation without writing a separate Python script, keeping the request within the same node-based environment as your other creative tasks. The supplied context includes a production function named display_atlas(document, out), but does not include its implementation or establish its exact relationship to the exposed tool. Consequently, the available evidence does not establish what the atlas contains, how it is arranged, or which file formats it produces. The verified behavior is that the node prepares a tool request, sends it to OpenKatana, and returns the response; treat it as an integration point for the atlas operation rather than a documented image-layout or texture-packing utility.
OpenKatana · Build display atlas Input Parameters:
project_id
A required STRING passed to the request-preparation helper alongside the tool identifier and your arguments. It supplies project context when the node prepares the OpenKatana request, so you should use the identifier associated with the project you intend to work on. The supplied code does not show how project identifiers are validated, whether the project must already exist, or how this value interacts with project information inside the arguments. No default value, permitted identifier format, minimum or maximum length, or list of options is provided in the supplied interface.
arguments
A required STRING containing the argument information that the node passes to OpenKatana’s request-preparation helper. This is the interface’s place for supplying the tool-specific request details, since no separate atlas configuration fields are exposed. The string is processed before the tool is invoked, but the supplied source does not show its required syntax, accepted keys, parsing rules, or defaults. Although the context contains the function signature display_atlas(document, out), that signature alone does not establish valid keys for this node’s argument string. Use the argument format documented for build_display_atlas in your installed OpenKatana version rather than assuming that those function parameter names are accepted. No default, length limits, or selectable options are shown.
after
An optional STRING accepted by the node’s execution method, with a Python default of None when omitted. In the displayed implementation, this value is not read, added to the prepared arguments, or passed to the tool invocation. Connecting it can provide a workflow dependency when the connection is accepted by ComfyUI, but the supplied code does not establish any additional ordering, status-checking, or error-handling behavior. Do not treat it as an atlas setting or assume that its text changes the result. No string default, length limits, or selectable options are shown.
OpenKatana · Build display atlas Output Parameters:
result_json
The node’s only output, declared as a STRING. The implementation passes the result of the OpenKatana tool invocation through a response helper before returning it, making this output the place to inspect the tool’s response. Its name indicates a JSON-oriented response, but the supplied code does not include the response helper or establish the exact serialization, field names, success structure, or error structure. Do not assume that it contains an image, a particular file path, or a fixed set of atlas metadata. Inspect the returned text before configuring downstream processing, and use a JSON parser only when the returned content is valid JSON.
OpenKatana · Build display atlas Usage Tips:
- Confirm the
build_display_atlasargument schema for your installed OpenKatana version before configuringarguments. The supplied interface does not expose verified atlas settings such as dimensions, spacing, layout, or output format. - Use the project identifier associated with your intended OpenKatana project. When working with several projects, check this value before execution to avoid sending the request with the wrong project context.
- Start with the smallest request supported by the tool’s documentation, inspect
result_json, and then add supported options one at a time. This makes it easier to identify which change caused a failure. - Do not substitute arguments from unrelated analysis or workflow tools. The supplied references to energy analysis, clip analysis, and scaling do not establish settings supported by this atlas node.
- Leave
afterdisconnected unless you need a workflow dependency. The displayed execution method does not use its text, so changing that text is not a way to control atlas generation. - Connect
result_jsonto a text-inspection node before building downstream automation. Verify the actual response fields rather than assuming a particular artifact path or success indicator.
OpenKatana · Build display atlas Common Errors and Solutions:
unexpected inputs: …
- Explanation: This is the explicit error pattern shown in the node’s source. The execution method raises a
TypeErrorwhen it receives additional named fields that are not part of its recognized typed inputs. An external caller, an incompatible workflow, or a modified node definition can introduce such fields. - Solution: Use only the exposed inputs:
project_id,arguments, and optionalafter. Put tool-specific settings intoargumentsonly in the format supported by OpenKatana, rather than adding new node sockets or execution keywords.
Required input missing: project_id or arguments
- Explanation: This is a descriptive troubleshooting label, not a verified error string from the implementation. Both inputs are required by the interface, so omitting either can prevent workflow validation or execution. The exact message depends on ComfyUI and how the node is called.
- Solution: Supply both required STRING inputs. Use your intended project identifier and an argument string that follows the installed tool’s documentation. A connected but empty string is not necessarily a valid value.
Argument parsing or validation failure
- Explanation: This is a possible failure category rather than a confirmed error message. The node processes
argumentsthrough preparation helpers before invoking OpenKatana. Unsupported syntax, unrecognized settings, or missing tool-required information may be rejected there, but the supplied source does not reveal the validation rules. - Solution: Compare your argument string with the documented
build_display_atlasschema. If that schema requires JSON, check its syntax with a JSON validator; do not assume JSON or particular property names solely from this node’s interface.
Project identifier rejected
- Explanation: This is a possible tool-level failure, not a verified message. The request-preparation helper receives
project_id, but its validation behavior is not shown. An incorrect or unavailable identifier may prevent the request from being prepared or executed. - Solution: Verify the identifier against the project information in your OpenKatana environment. Check for accidental spaces, copied labels instead of identifiers, or a project belonging to a different environment.
Tool invocation fails
- Explanation: This is a general troubleshooting category, not an exact error string. The node delegates execution to an OpenKatana call, so failures may occur beyond the visible wrapper. The provided code does not establish service requirements, installation checks, or the underlying atlas tool’s error messages.
- Solution: Inspect the ComfyUI execution log and any returned response for the specific cause. Confirm that your installed OpenKatana version provides
build_display_atlasand that your workflow matches that version’s interface before changing atlas-related arguments.
result_json does not contain the expected image or path
- Explanation: The declared output is a STRING, not a ComfyUI IMAGE output, and its response schema is not shown. A downstream node can fail if it expects image data or a file-path field that the response does not provide.
- Solution: Inspect the returned text first. If it contains a documented artifact path, extract that value and use an appropriate loader; if it contains an error or status response, address that response before continuing. Do not assume that the output string itself is an image or a filesystem path.
