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
# Create comprehensive guide on how to initialize FUSE by analyzing case files and parameter structures
716
+
claude "Write a how_to_init_fuse.md knowledge file, structured for users and LLMs to learn how to define FUSE use cases. You should looking at each individual *.jl files under FUSE/src/cases (don't skip any, they are all important!). Also add a note about the parameters definitions being in FUSE/src/parameters/parameters_inits.jl and use this file to build your .md documentation as necessary."
717
+
718
+
# @devs
719
+
learn_actors_docstrings:
720
+
# update actors docstrings
721
+
claude "Go through each and every actor file (***_actor.jl) and (in parallel) spawn a claude session to improve the docstring of each. \
722
+
Don't add any docstring to the \`@actor_parameters_struct\` or the Actor constructor. \
723
+
Instead you should focus on the \`ActorXXX(dd,act)\` function which in the end is what is going to appear in the online documentation. \
724
+
You can add some extra details to the docstrings of \`_step()\` and \`_finalize()\`. \
725
+
NEVER document boilerplate arguments, like \`dd\`, \`par\`, \`act\`, \`kw...\`. \
726
+
To know what an actor does, look at the executable code. \
727
+
If there's already a docstring, verify it against the executable code. \
728
+
If there's any conflicting information the executable code should take precendence. \
729
+
To know what actors need documentation, search for \`actor_parameters_struct\`, and process them in parallel claude sessions."
# Some fields in the data dictionary are expressions (ie. Functions).
366
-
# For example `dd.core_profiles.profiles_1d[].pressure` is dynamically calculated as the product of thermal densities and temperature with addition of fast ions contributions
# In addition to evaluating expressions by accessing them, expressions in the tree can be evaluated using `IMAS.freeze(ids)`
376
-
#
377
-
# NOTE: `IMAS.freeze(ids, field::Symbol)` works on a single field and `IMAS.refreeze!(ids, field)` forces re-evaluation of an expression. Also, `IMAS.empty!(ids, field::Symbol)` can be used to revert a frozen field back into an expression.
# We can introduce a change in the `dd1` and spot it with the `diff` function
383
-
384
-
dd1.equilibrium.time_slice[1].time =-100.0
385
-
IMAS.diff(dd.equilibrium, dd1.equilibrium)
217
+
# Understanding how to work with the IMAS data structure is a must for working within the FUSE ecosystem!
386
218
387
219
# ## Summary
388
220
# Snapshot of `dd` in 0D quantities (evaluated at `dd.global_time`).
389
221
#
390
222
# Extract + plots saved to PDF (printed to screen if `filename` is omitted). NOTE: For PDF creation to work, one may need to install of `DejaVu Sans Mono` font.
0 commit comments