home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!howland.reston.ans.net!hsdndev!newsfeed.rice.edu!rice!dawn.cs.rice.edu!preston
- From: preston@dawn.cs.rice.edu (Preston Briggs)
- Newsgroups: comp.arch
- Subject: Re: How to list software as reference
- Message-ID: <BzJ96n.Iuv@rice.edu>
- Date: 20 Dec 92 00:54:22 GMT
- References: <2B33B7B3.15688@news.service.uci.edu>
- Sender: news@rice.edu (News)
- Organization: Rice University, Houston
- Lines: 24
-
- jtien@verdi.eng.uci.edu (Joe Tien) writes:
-
- >How should I list software packages/programs I used in my research as
- >references? They are even more significant than the papers I read in
- >terms of getting actual results and stuff.
-
- Usually, you describe your experiments (and stuff) in a section called
- something like "Experiments" or "Emperical Results". As part of the
- description of the experiments, you mention all the relevant software.
-
- For example, if you're collecting SPECmarks, you should describe the
- machines, the compilers, the compiler flags, and the exact verion of
- the SPEC programs -- enough so others could reproduce your results.
-
- Some tools, e.g., gprof, are described in papers or technical reports.
- Try and cite the papers if possible, since not every reader (or
- referee!) will be familiar with all the tools available on your
- system.
-
- You don't bother mentioning that you used gnu to type up shell scripts
- run on bash or that you typeset the paper using LaTeX; those details
- just aren't relevant.
-
- Preston Briggs
-