Sienna-Platform / Sienna-Platform/PowerOperationsModels.jl
Construct Device is a Runtime call
Open
Nobody has claimed this yet.
performance
- Dominant language
- Julia
- Stars
- 2
- Forks
- 1
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 26
Description
^ %185 = < constprop > getproperty(::TimerOutput{…},::Symbol{…})::Bool
get_component_type(device_model::DeviceModel)
"$(get_component_type(device_model::DeviceModel)::Type{D} where D<:De…
TimerOutputs.@timeit BUILD_PROBLEMS_TIMER "$(get_component_type(devic…
%194 = gc_bytes()::Int64
%195 = time_ns()::UInt64
validate_available_devices(device_model::DeviceModel, sys)
ArgumentConstructStage()
• %207 = runtime < construct_device!(…,…,…,…,…)::Any >
v %221 = < concrete eval > getproperty(::LogLevel{…},::Symbol{…})::…
[ Info: This is a runtime call. You cannot descend into it.
Making an exploration with Ctuchulu.jl I got to this point when looking for performance issues.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report points to construct_device! in the ArgumentConstructStage path, after validate_available_devices and get_component_type, and was found with Ctuchulu.jl. Start by reproducing that exploration and locating the implementation; done should include a concrete change for the runtime call and evidence that the performance issue is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100