Document

🔴 Red sticky = I need help. Put it up the moment you are stuck — an instructor will come to you.

🟢 Green sticky = I have done 1–4 and am moving on to the bonus work, and I am ready to help my table.

Day 2 arc — you are on step 2, document. profile document submit read logs scale (Part 2) debug 1 2 3 4 5

Everything on this page runs from your clone, with the environment active:

cd ~/yens-onboarding-2026
source .venv/bin/activate

Task: Write down the resources you measured for the 10-filing run in your README.

Now that you’ve profiled 10 filings, write down what you measured. Open the README.md in your repo and add a Resource Profile section:

## Resource Profile

### extract_form_3_batch.py — 10 filings

- Yen node used:
- Wall-clock time (real):
- CPU cores used:
- RAM used (RES from htop, in MB or GB):
- Serial or parallel:

Fill in the actual numbers from your time, userload, and htop output.

Five fields, and three of them are the ones that matter next: the wall-clock time, the cores and the RAM become the --time, --cpus-per-task and --mem of the job you submit on the next page. That is why they are worth writing down rather than trusting to memory. The node and serial-or-parallel are for you — context for reading these numbers again in a month.

Finish all four pages before you start any bonus. The numbers you write down on one page are the inputs to the next, and Part 2 assumes all four are done.

⭐ Bonus — let Claude write it into the README

You already have the numbers. Turning them into a formatted README section is the tedious half — hand that to Claude.

Start Claude Code in your repo:

ml claude-code
cd ~/yens-onboarding-2026
claude

Then give it your measurements. The <...> are placeholders — replace the whole thing, brackets included: yen2, not <yen2>.

> Add a "Resource Profile" section to README.md for scripts/extract_form_3_batch.py over 10 filings: ran on <node>, real <wall-clock time>, <cores> cores, <RAM> RES, <serial or parallel>. Add just that section and leave the rest of the file alone.

Read the diff before you approve it. Two things to check:

  • The numbers are yours. Claude did not watch your run, so any figure you do not hand it, it will invent — and it will look reasonable. That matters more here than anywhere else today: these numbers become the --time and --mem on the next page, so a made-up one turns into a job that gets killed or waits far longer than it needs to.
  • Nothing else moved. You asked for one section added, not a tidied-up README.

Then /exit to get your shell back, and check the result:

cat README.md

Page last modified: Sep 17, 2026.

Your details

Set these once and the commands on every page fill themselves in. Stored in this browser.

Built with Just the Docs.