Skip to content

docs: convert two ordered lists to bullets (phase M) #936

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ocots merged 1 commit into from
Sep 1, 2026
Merged

docs: convert two ordered lists to bullets (phase M) #936

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions src/helpers/component_completion.jl
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,10 @@ $(TYPEDSIGNATURES)
Complete missing resolution components using the registry.

This function orchestrates the component completion workflow:
1. Extract symbols from provided components using `_build_partial_description`
2. Complete the method description using `_complete_description`
3. Resolve method with parameter information using `CTBase.Orchestration.resolve_method`
4. Build or use strategies for each family using `_build_or_use_strategy`
- Extract symbols from provided components using `_build_partial_description`
- Complete the method description using `_complete_description`
- Resolve method with parameter information using `CTBase.Orchestration.resolve_method`
- Build or use strategies for each family using `_build_or_use_strategy`

# Arguments
- `discretizer::Union{CTSolvers.DOCP.AbstractDiscretizer, Nothing}`: Discretization strategy or `nothing`
Expand Down
6 changes: 3 additions & 3 deletions src/solve/dispatch.jl
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,9 @@ $(TYPEDSIGNATURES)
Main entry point for optimal control problem resolution.

This function orchestrates the complete solve workflow by:
1. Detecting the resolution mode (explicit vs descriptive) from arguments
2. Extracting or creating the strategy registry for component completion
3. Dispatching to the appropriate Layer 2 solver based on the detected mode
- Detecting the resolution mode (explicit vs descriptive) from arguments
- Extracting or creating the strategy registry for component completion
- Dispatching to the appropriate Layer 2 solver based on the detected mode

# Arguments
- `ocp::CTModels.AbstractModel`: The optimal control problem to solve
Expand Down
Loading