A barometer shop’s generate button must produce a still from nothing on disk. How should that program path be implemented?
Select an answer to reveal the explanation.
Short Explanation
Nothing on disk means you start with random static, then let the denoiser clear the fog into a still. That’s the generate path—not reloading yesterday’s photo.
Full Explanation
A generate button that must produce a still from nothing on disk implements sample noise, run the denoiser, and write a picture—starting from a random field. That path is correct for the barometer shop’s noise-to-image skill. Civic generative tools that claim noise-to-image must actually start from noise, not from yesterday’s photo.
Loading yesterday’s photo and calling it noise-to-image generation fails the noise-start requirement. Running only a Domain 1 step-count trial with no generate call fails implementation. Skipping sampling and feeding empty file paths into CLIP as if they were images fails both generation and CLIP usage.
Exam caveat: noise-to-image means sampling noise then denoising to a still. Operational check: verify civic generate paths sample noise (with optional seed), denoise, and write outputs—reject photo-reload labeled as noise generation. Align this choice with the agency’s published multimodal runbook so civic operators can audit why the configuration was accepted. Record the civic software choice in the service README—named modules, inputs, and domain—so operators can replay the same path during audits and handoffs. Prefer explicit, reversible civic decisions over silent assumptions when multimodal data or software paths move toward production.