Skip to content

Hello-QM/catgo-LRG / server/catgo/workflow

catgo-workflow

Verified

Create and manage computational chemistry workflows with CatGo. Supports VASP, CP2K, ORCA, MLP, LAMMPS. Build OER/HER/CO2RR workflows, geometry optimization, frequency analysis, Gibbs energy calculations.

FileKindSize
SKILL.mdskill md3.8 KB
__init__.pyscript1.1 KB
builtins.pyscript4.7 KB
builtins_impl.pyscript21.2 KB
config.pyscript6.5 KB
db.pyscript25.3 KB
engine/__init__.pyscript615 B
engine/advancer.pyscript9.3 KB
engine/ai_diagnosis.pyscript3.8 KB
engine/batch_submitter.pyscript9.7 KB
engine/broadcast.pyscript1.8 KB
engine/collector.pyscript8.3 KB
engine/control_flow.pyscript5.7 KB
engine/engine_builtins.pyscript19.6 KB
engine/engine_registry.pyscript1.5 KB
engine/error_handler.pyscript3.6 KB
engine/hpc_utils.pyscript4.0 KB
engine/job_script.pyscript11.6 KB
engine/lifecycle.pyscript10.8 KB
engine/orca_progress.pyscript3.4 KB
engine/poller.pyscript11.7 KB
engine/resolver.pyscript2.7 KB
engine/result_collector.pyscript56.3 KB
engine/result_handler.pyscript5.6 KB
engine/scanner.pyscript52.0 KB
engine/smart_recovery.pyscript3.6 KB
engine/submitter.pyscript26.2 KB
engine/v1_monitor.pyscript2.7 KB
engine/vasp_submission.pyscript29.0 KB
graph_converter.pyscript6.5 KB
mcp_tools.pyscript7.5 KB
provenance.pyscript5.8 KB
reference.pyscript1.1 KB
service.pyscript4.0 KB
state_map.pyscript1.5 KB
states.pyscript7.5 KB
task_decorator.pyscript2.5 KB
task_ids.pyscript986 B
v1_compat.pyscript2.8 KB
workflow.pyscript12.0 KB

engine/v1_monitor.py

View on GitHub
"""Translate V2 engine broadcast messages to V1 frontend wire format.

V1 wire format (consumed by workflow-execution.svelte.ts):
  - initial_state: {type, workflow_status, steps: [{id, status, hpc_job_id, error_message}]}
  - step_status:   {type, step_id, status, job_id?}
  - workflow_status: {type, status}
  - ping:          {type: "ping"}

V2 broadcast format (from broadcast.py):
  - task_status:    {type, task_id, status}  (status is UPPERCASE)
  - workflow_status: {type, status}          (status is lowercase)
"""

from __future__ import annotations
from typing import Any

from catgo.workflow.state_map import v2_to_v1_status
from catgo.workflow.task_ids import node_id_from_task_id


def build_initial_state(
    workflow_status: str,
    tasks: list[dict],
) -> dict[str, Any]:
    """Build V1-shaped initial_state message from V2 task rows."""
    steps = []
    for t in tasks:
        steps.append({
            "id": t.get("node_id") or t["id"],
            "node_type": t.get("task_type", ""),
            "status": v2_to_v1_status(t["status"]),
            "hpc_job_id": t.get("hpc_job_id"),
            "error_message": t.get("error_message"),
        })
    return {
        "type": "initial_state",
        "workflow_status": workflow_status,
        "steps": steps,
    }


def translate_broadcast_message(
    msg: dict[str, Any], workflow_id: str | None = None
) -> dict[str, Any]:
    """Translate a V2 broadcast message to V1 wire format.

    V2 broadcasts carry the namespaced task id (`{workflow_id}:{node_id}`); the
    V1 frontend keys steps by graph node id, so de-namespace via the passed
    workflow_id before emitting `step_id`.
    """
    msg_type = msg.get("type", "")

    if msg_type == "task_status":
        return {
            "type": "step_status",
            "step_id": node_id_from_task_id(msg.get("task_id", ""), workflow_id),
            "status": v2_to_v1_status(msg.get("status", "")),
            "job_id": msg.get("job_id"),
        }

    if msg_type == "step_message":
        return {
            "type": "step_status",
            "step_id": node_id_from_task_id(msg.get("task_id", ""), workflow_id),
            "status": "running",
            "message": msg.get("message", ""),
        }

    if msg_type == "workflow_status":
        return {
            "type": "workflow_status",
            "status": msg.get("status", ""),
        }

    # Pass-through (ping, error, and step_status/step_log broadcast directly by
    # local execution engines). Those carry a namespaced step_id that the V1
    # frontend keys by graph node id, so de-namespace it here too.
    if "step_id" in msg:
        return {**msg, "step_id": node_id_from_task_id(msg.get("step_id", ""), workflow_id)}
    return msg
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall