It's UWAweek 26 (mid-year break)


This forum is provided to promote discussion amongst students enrolled in Open Source Tools and Scripting.

Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.

How do I ask a good question?
Displaying selected article
Showing 1 of 439 articles.
Currently 4 other people reading this forum.

 UWA week 20 (1st semester, week 11) ↓
SVG not supported

Login to reply

11:26am Wed 15th May, Michael W.


Dear Professor, I got confused after reading the threads. I want to clarify again about the input of the best_predictor script: I understood that when: ./cantril_data_cleaning file1 file2 file3 --> The result will be sent to stdout.

But for the best_predictor script, you said that "the input to best_predictor will be a TSV file" so it means that for the cantril_data_cleaning, we will send the output both to stdout and a TSV file and then that TSV file is used as the input for best_predictor. Is that correct?

For example: ./cantril_data_cleaning file1 file2 file3 . Besides printing to the stdout, it will also print the output to another file like sample1.tsv --> Then we will: ./best_predictor sample1.tsv to report to stdout mean correlation ... like the sample

Thank you so much for your clarification!

Hi, The requirements are:

  • cantril_data_cleaning output is sent to standard output; input is from the 3 TSV format files
  • best_predictor takes a TSV format file of cleaned data, and sends the output of the analysis to standard output

##Reasoning## Having the output from cantril_data_cleaning go to stdout means that the user can choose to redirect stdout to a file of their choice, rather than trying to figure out what name the programmer has chosen, so while stdout - by default - prints to the screen, in practice it will generally be redirected into a file.

Fair enough?

Cheers MichaelW 👨‍🎨

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  5:07AM Sep 06 2023
Privacy policy