Home
last modified time | relevance | path

Searched refs:CI (Results 1 – 11 of 11) sorted by relevance

/petsc/src/tao/constrained/tutorials/
H A Dex1.c62 Vec x, G, CI, CE; in main() local
123 PetscCall(MatCreateVecs(user.Ai, NULL, &CI)); in main()
124 PetscCall(FormInequalityConstraints(tao, user.x, CI, (void *)&user)); in main()
126 PetscCall(VecView(CI, PETSC_VIEWER_STDOUT_WORLD)); in main()
128 PetscCall(VecDestroy(&CI)); in main()
351 PetscErrorCode FormInequalityConstraints(Tao tao, Vec X, Vec CI, PetscCtx ctx) in FormInequalityConstraints() argument
371 PetscCall(VecSetValue(CI, 0, ci, INSERT_VALUES)); in FormInequalityConstraints()
373 PetscCall(VecSetValue(CI, 1, ci, INSERT_VALUES)); in FormInequalityConstraints()
376 PetscCall(VecAssemblyBegin(CI)); in FormInequalityConstraints()
377 PetscCall(VecAssemblyEnd(CI)); in FormInequalityConstraints()
/petsc/src/tao/interface/
H A Dtaosolver_bounds.c493 PetscErrorCode TaoComputeInequalityConstraints(Tao tao, Vec X, Vec CI) in TaoComputeInequalityConstraints() argument
498 PetscValidHeaderSpecific(CI, VEC_CLASSID, 3); in TaoComputeInequalityConstraints()
500 PetscCheckSameComm(tao, 1, CI, 3); in TaoComputeInequalityConstraints()
501 PetscCall(PetscLogEventBegin(TAO_ConstraintsEval, tao, X, CI, NULL)); in TaoComputeInequalityConstraints()
502 …inequality constraints", (*tao->ops->computeinequalityconstraints)(tao, X, CI, tao->user_con_inequ… in TaoComputeInequalityConstraints()
503 PetscCall(PetscLogEventEnd(TAO_ConstraintsEval, tao, X, CI, NULL)); in TaoComputeInequalityConstraints()
/petsc/lib/petsc/bin/maint/
H A Dcheck-ci-settings.sh4 echo Skipping as this is MR CI for "${CI_MERGE_REQUEST_TARGET_BRANCH_NAME}" branch
/petsc/doc/developers/
H A Ddevelopment.md14 encouraged* that you `configure` with this option. CI will already have it enabled,
H A Dtesting.md333 load, especially in CI.
345 to prevent it from being output when the CI test harness is running.
533 This method can also be used for the PETSc continuous integration (CI) pipeline jobs. For failed jo…
H A Ddocumentation.md181 are used in the {any}`PETSc CI<test_harness_data>`.
/petsc/doc/developers/contributing/
H A Dpipelines.md3 # GitLab CI Pipelines
H A Ddevelopingmr.md145 Ideally, each commit in an MR will pass the PETSc CI testing, while presenting a small-as-possible …
/petsc/lib/petsc/bin/maint/petsclinter/petsclinter/
H A DREADME.rst18 what clang can compile**. For this reason, the CI run of the linter needs to have almost
/petsc/doc/changes/
H A D321.md22 …b/petsc/bin/maint/runjobs.py list-of-jobs script to allow submitting a subset of the jobs to the CI
/petsc/doc/community/meetings/2023/
H A Dindex.md151 - {any}`GitLab CI pipelines<pipelines>`
162 - {any}`testing system including the GitLab CI<test_harness>`