You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a regular simulation (kernels & bcs directly in the input file), I can see from Debug/show_actions exactly what is happening during the setup. The name of the kernels appear as they are created.
With Components and Actions, I dont know what's being created. The very least I would need would be:
name
type
But I would also like to be able to check:
block / boundary restriction. This could be done AFTER the setup (and I suggest we do that instead)
which variables are coupled in. This could also be done after
Steps to Reproduce
Run any simulation with Debug/show_actions with first kernel/bc syntax then with Actions
Impact
Lack of clarity can defeat user debugging and force developer intervention.
The text was updated successfully, but these errors were encountered:
GiudGiud
added
P: minor
A defect that does not affect the accuracy of results.
T: defect
An anomaly, which is anything that deviates from expectations.
labels
Oct 25, 2023
Bug Description
In a regular simulation (kernels & bcs directly in the input file), I can see from Debug/show_actions exactly what is happening during the setup. The name of the kernels appear as they are created.
With Components and Actions, I dont know what's being created. The very least I would need would be:
But I would also like to be able to check:
Steps to Reproduce
Run any simulation with Debug/show_actions with first kernel/bc syntax then with Actions
Impact
Lack of clarity can defeat user debugging and force developer intervention.
The text was updated successfully, but these errors were encountered: