Skip to content

Commit bbed14b

Browse files
committed
Merge remote-tracking branch 'origin/claude/issue-528-petab1to2-validate-740e55' into claude/issue-528-petab1to2-validate-740e55
2 parents 4059541 + 9663aff commit bbed14b

1 file changed

Lines changed: 5 additions & 10 deletions

File tree

‎petab/v2/petab1to2.py‎

Lines changed: 5 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -51,16 +51,11 @@ def petab1to2(
5151
The output directory to save the converted PEtab problem, or ``None``,
5252
to return a :class:`petab.v2.Problem` instance.
5353
:param validate:
54-
Whether to lint the PEtab v1 problem before and the generated
55-
PEtab v2 problem after the conversion.
56-
If ``True`` (default), the conversion fails if either does not pass
57-
linting.
58-
If ``False``, both lint steps are skipped. This allows converting
59-
problems that fail linting for reasons unrelated to the conversion,
60-
e.g., a visualization table referencing non-existent datasets or an
61-
intentionally incomplete model. In this case, the result should be
62-
checked separately, e.g., using ``petablint``.
63-
The YAML file is validated against the PEtab v1 schema in either case.
54+
Whether to lint the input PEtab v1 problem, and the
55+
output PEtab v2 problem.
56+
If ``True`` (default), both problems are validated.
57+
If ``False``, neither problem is validated.
58+
The ``yaml_config`` content is validated regardless.
6459
6560
:raises ValueError:
6661
If the input is invalid or, if ``validate`` is ``True``, if the input

0 commit comments

Comments
 (0)