Turn a Research Description into a Figure Brief
Define the question, relationships, labels, and review steps before generating a scientific diagram in FigEditor.
A paragraph explains a study; a figure brief defines objects, connections and exclusions. Converting one into the other requires an intermediate structure. Otherwise a model may turn “associated with” into a causal arrow or invent a sample count to make a workflow look complete.
Start with a fictional input paragraph
Samples are collected and checked for quality. Retained samples enter analysis; excluded samples are logged separately. The analysis output is reviewed before reporting. Counts are not yet finalized.
This teaching paragraph deliberately contains no real study data. Extract five objects: Collection, Quality check, Analysis, Review and Exclusion log. Define four main-path connections and one branch. Reporting can be a separate final object if it must appear; decide that before generation.
| Connection | Meaning | Required label |
|---|---|---|
| Collection → Quality check | Procedure order | None |
| Quality check → Analysis | Selection branch | Retained |
| Quality check → Exclusion log | Selection branch | Excluded |
| Analysis → Review | Output handoff | None |
| Review → Reporting | Approved handoff | Approved |
An arrow should communicate the listed relation, not a result that is absent from the paragraph.
Resolve ambiguity before drawing
What happens if review fails? The paragraph does not say. Do not add a feedback loop by assumption. Ask the protocol owner or mark the draft as incomplete. Likewise, “quality” needs an operational definition in the methods even if the diagram uses a short label.
Separate labels from instructions. Labels are the exact strings the reader will see; instructions explain position, arrow semantics and omissions. This prevents prose such as “put this on the right” from becoming accidental figure text.
Submit a constrained brief
A proposed prompt for the fictional paragraph is:
Draw an explanatory workflow. Main path, left to right: Collection → Quality check → Analysis → Review → Reporting. From Quality check, add a downward branch to Exclusion log. Label the arrow into Analysis “Retained,” the arrow into Exclusion log “Excluded,” and the arrow into Reporting “Approved.” Arrows indicate procedure or selection only. Add no sample counts, percentages, performance curves, feedback loops or biological mechanisms. Use plain boxes and legible labels. Leave room for a caption explaining the quality criteria.
This prompt has not been generated or validated here. Use your verified protocol instead of the fictional content in the figure workspace. Keep the exact prompt actually sent to the model, including every constraint and reference input.
Validate the output as a small graph
Count six boxes, five main-path/branch connections in total, and three branch/handoff labels. Follow the Retained path from Collection to Reporting. Confirm that the Excluded path ends at Exclusion log and never reconnects to Analysis. Then read labels character by character.
If the tool returns a raster image, treat every label as pixels until proven otherwise. If it returns or converts to SVG, select a label in the SVG editor and confirm that you can change one word. A file containing an embedded picture is still not a six-object editable diagram.
Make one revision at a time
When review requires a feedback loop, first change the verified protocol and connection table, then update the drawing. Keep the old brief so reviewers can see why the structure changed. Use the layout tool only when combining this workflow with other approved panels. The useful output is a diagram whose branch logic matches the study, with a readable caption and traceable versions.