Save a repeatable script

Save a repeatable script — guided practice

Turn the checked pipeline into a script that writes a dedicated result file.

Create an empty shell-lab folder. Inside it create input and output folders. Put registrations.tsv in input with these tab-separated rows and a final newline: session<TAB>status; art<TAB>confirmed; code<TAB>confirmed; art<TAB>waiting; code<TAB>confirmed; music<TAB>confirmed. Start the terminal in shell-lab. Bash required; no sudo, remote systems or deletion commands. Put the supplied summarize.sh in shell-lab. It changes to its own folder before reading input. Do not run downloaded unknown scripts.

1. 1. Read before running

   Open summarize.sh and identify its input and output paths.

   You should see: It checks that input/registrations.tsv is readable before writing output/confirmed.txt.

   Reviewing a script reveals its effects before execution.

2. 2. Run with Bash

   Execute bash summarize.sh from shell-lab.

   bash summarize.sh

   You should see: The command finishes and output/confirmed.txt exists.

   Explicit Bash avoids relying on execute permissions.

3. 3. Inspect saved output

   Print output/confirmed.txt.

   cat output/confirmed.txt

   You should see: Counts are art 1, code 2 and music 1.

   Successful execution alone does not prove useful output.

4. 4. Explain redirection

   Write that > replaces this dedicated output file on each run.

   You should see: The script recreates one report rather than appending duplicates.

   The target must be disposable output, never the raw input.