Jeffrey Newman

I definitely do not normally manually run `~/.cache/pre-commit/repoxlgredg0/py_env-python3.13/bin/ruff`, I let pre-commit do that for me, which is kind of the point of pre-commit, right? An hour ago just before my...

Example outputs from the SANDAG test model: - [Component-level profile](https://www.driftless.xyz/share/example-sandag-profiling/expression-timing-components.html) - [Subcomponent-level profile](https://www.driftless.xyz/share/example-sandag-profiling/expression-timing-subcomponents.html) Or: [Linked here](https://driftlesslabs-my.sharepoint.com/:f:/g/personal/jeff_driftless_xyz/EokXjdc9iv9Ip4-qT5t-JnoBqfSirACYYYl9RmEJO-b_0w?e=DQAJtz). Note: if you want to see the results, you'll need to click the first...

@stefancoe @dhensle I have found and fixed the problem you observed, which turns out was a Windows thing. I added a GitHub actions test that runs the expression profiling on...

@bwentl I like your idea, although it's not a very simple change to implement. Due to potential preprocessing of spec files to remove zero-result rows, we cannot infer the SPEC...

> I think the functionality should be updated to delete old timing files before writing new ones. I imagine users potentially want to keep older expression timing results around to...

Should now be working as described above, with a timestamped log file.

@JoeJimFlood 1. I will look into that error message, and see if I can fix it. 2. Runtime on this was 7078 seconds. How long does it take to run...

Oh, we should not have all those timestamped directories... that's a bug I will fix. There should only be a single timestamp for the entire multiprocessor run, stamped at the...

@JoeJimFlood Yes, your most recent message looks correct. @dhensle Since you previously "request changes", I am blocked from merging this until you now approve it.

@dhensle I made the update to the docs in this PR