Use a Litmus handoff to review a study design, request preparation, approve a draft order request, and bring results back into the project. These controls appear only when Litmus is available for your Marvin environment.
Only the project owner can request preparation or approve submission.
Connect Litmus
Open account Settings, select Integrations, then select Litmus Science and follow Connect services and model providers. Approve the access needed to create, view, update, and submit draft order requests.
If the connection says Admin setup, a Marvin administrator must configure Litmus first. If Litmus later refuses a permission, select Update permissions on the existing connection.
Open a study design
- Open the project and select Data.
- Under Research Documents, select a file named
docs/study_design_*.md. - Find Litmus handoff above the file preview.
Choose one path:
- Prepare for Litmus creates a handoff revision and queues preparation for a research run that started with Litmus connected. It does not submit an order request.
- Prepare package lets you choose constraints, attachments, and open questions, then build a reviewable package. Downloading the package sends nothing to Litmus.
If you have more than one Litmus connection, choose the connection for this handoff.
Follow the preparation request
The request line shows its current state:
- Queued for preparation, Adopted, or In progress: preparation is still underway.
- Blocked: open Review and resolve the listed decisions, or prepare a new revision when that action is offered.
- Ready for approval: select Review before deciding whether to submit.
- Submitted or Failed: select Review to inspect the recorded outcome.
Preparing or queuing the request does not submit it to Litmus.
Review the request
In Approve Litmus submission:
- Read the objective and context that will be sent.
- Review each assay and requirement.
- For an assay you want included, select Mark in scope, enter a reason, and save it.
- Answer any open requirement decisions. The evidence note stays in Marvin.
- Use Refresh status if the remote state may have changed.
Select Hold when Marvin should revise the request. Add a specific instruction if needed; the instruction is queued for research and does not submit anything.
Approve and submit
When Litmus reports that the request is ready for submission, select Approve and submit. This is the action that submits the displayed request.
If the request changed since you opened it, Marvin refreshes the review. Read the new version before approving again.
If Marvin says the submission may have reached Litmus, do not submit another request. Select Refresh status. If the state remains uncertain, open Litmus and check the order request before retrying.
Track the order request
Open the handoff revision under the study design.
- Refresh status reads the current Litmus status.
- Open in Litmus opens the remote request when a link is available.
- Read from Litmus refreshes the order request and its requirements.
- Send answers to Litmus sends saved answers after you review the prepared message.
- Reconcile with Litmus checks an uncertain send when that action is available.
If an outcome is unknown, Marvin avoids sending the same message again. Check or reconcile the existing request before preparing a new attempt.
Import results
Results import into one experiment batch.
- Under Results, choose the experiment batch.
- Select Associate batch and confirm. This association cannot be changed later.
- When results are available, select Fetch results.
Marvin reports whether the result was complete, partial, failed, or already imported. Partial and failed imports do not add result files to the selected experiment batch.
Receive Litmus event updates
Under Event hooks, select Create hook. If Register with Litmus is available, select it to register the hook. Until the hook is registered and Marvin can verify its events, use Refresh status and Read from Litmus instead.
Use Rotate secret when Litmus offers it for the hook. Revoke stops Marvin from accepting events at that URL; it does not remove a registration already stored in Litmus.