Distributed Model Name:
DistributedModelName is a utility node that passes text to a helper for logging and returns the helper’s result to the workflow, along with information for display in the interface. Its name suggests a role in identifying a model in a distributed workflow, but the provided source does not show the helper’s implementation. You should therefore treat its confirmed purpose as recording the supplied text through that helper, rather than assume it loads a model, checks a model name, or coordinates work across GPUs.
Distributed Model Name Input Parameters:
text
The string you want the node to pass to its logging helper. The default is an empty string (''). No minimum length, maximum length, or set of allowed values is specified in the provided source. Enter the model name or other identifying text you intend to record; changing this value changes what the helper receives, although the source does not show how the helper stores or displays it.
Distributed Model Name Output Parameters:
output
A single output socket with the flexible type *. The node fills it from the result returned by its logging helper. Because that helper’s implementation is not included, the exact value and its type cannot be determined from the provided source. Check the value in your workflow before connecting it to a node that requires a specific data type.
Distributed Model Name Usage Tips:
- Enter a clear, consistent name in
textso you can recognize what you intended to record when reviewing a workflow. For example, use the same spelling each time you refer to the same model. - Replace the default empty string when you need a meaningful label. The provided source does not establish whether an empty value is rejected or how it appears in the interface.
- Treat this as a text-logging utility, not a model loader. There are no performance or distributed-processing settings exposed by this node.
Distributed Model Name Common Errors and Solutions:
Node fails while processing text
- Explanation: The node passes
textto an imported logging helper whose implementation is not provided. The source does not establish a specific error message or which values, if any, the helper rejects. - Solution: Check that
textcontains the intended text and read the full error shown by your workflow. If the failure persists, inspect the helper or share the exact error message with the node maintainer.
A connected node rejects output
- Explanation: The output socket accepts any type, but that does not guarantee its returned value matches the type required by the next node. The exact returned value is not visible in the provided source.
- Solution: Inspect the value produced in your workflow and connect it only to a compatible input. Use an appropriate conversion node if one is available.
The displayed or returned value is not what you expected
- Explanation: The node returns both a helper-provided result and helper-provided interface data. The provided source does not define their contents, so it cannot establish an expected display format or guarantee that
outputrepeatstext. - Solution: Confirm the text you entered, then check the actual node result. Consult the logging helper’s documentation or implementation before relying on a particular format.
