Auditing Research: What Does It Mean and Why Is It Important?

  • Thread starter Thread starter mesa
  • Start date Start date
Click For Summary

Discussion Overview

The discussion revolves around the concept of auditing research, particularly in the context of maintaining detailed notes and the implications of such audits. Participants share personal anecdotes related to their experiences with note-taking and the casual use of language, including expletives, in their documentation. The conversation touches on the importance of transparency in research funded by public money and the ethical considerations involved in auditing practices.

Discussion Character

  • Exploratory
  • Debate/contested
  • Technical explanation

Main Points Raised

  • Some participants express frustration with the requirement to keep detailed notes, suggesting that it can feel punitive when audits are involved.
  • Others recount humorous experiences involving the use of expletives or casual language in their notes or reports, highlighting the informal nature of their documentation.
  • A participant notes that auditing is often associated with ensuring that public funds are used appropriately, particularly in experimental research settings.
  • There is mention of the potential for audits to check if research teams follow proper procedures to identify and correct mistakes, rather than simply looking for errors.
  • Some participants question the necessity and implications of audits in theoretical versus experimental research contexts.

Areas of Agreement / Disagreement

Participants do not reach a consensus on the nature and implications of research audits. While some agree on the importance of accountability in research funded by public money, others express concern about the punitive nature of audits and the casual approach to note-taking.

Contextual Notes

Participants highlight the variability in auditing practices across different types of research, noting that while some experiences are anecdotal, they reflect broader concerns about transparency and accountability in research funding.

Who May Find This Useful

This discussion may be of interest to researchers, students in STEM fields, and professionals involved in project management or research compliance, particularly those navigating the complexities of documentation and auditing in their work.

mesa
Gold Member
Messages
694
Reaction score
36
It seems okay to make good use of expletives in notes when needed.
imho
 
Physics news on Phys.org
Like "Dang", "Crud", and "Holy Molley"?
 
256bits said:
Like "Dang", "Crud", and "Holy Molley"?

Let us not forget 'dag-nabbit!' :)
 
What are you talking about?
 
dipole said:
What are you talking about?

I was having some frustration with a problem I was working on so took it out on my notebook.
 
I once did a research project where I was instructed to keep detailed notes on my work in a notebook. The writing style was... let's call it casual. At the end the professor in charge informed me that the grant required that I turn the notebook over in case anybody wanted to audit the work I did during the project. It is now in the possession of the federal government.
 
I had a similar experience. Project management wanted my notebook containing detailed derivations for a complicated software model of a physical process. About ten pages in the middle of the notebook contained pages marked with a big X across the page, plus some descriptive words. The first couple pages used colorful terms related to bodily waste. After that it was just "WRONG," "STILL WRONG," "YEP. THIS IS WRONG, TOO", and finally, "ALL THAT WRONG <deleted> STOPS HERE."

It was received with some level of amusement.
 
Have you ever used expletives in your code? Like printf("An **** programmer wrote it.\n") or puts("*** again?"); ?

I did in the past. Then a fried o mine (owner of a small software company at the time) told me a story about how he was asked by a prospective client to show him an alpha version of the software they were working on...
 
Borek said:
Then a fried o mine (owner of a small software company at the time) told me a story about how he was asked by a prospective client to show him an alpha version of the software they were working on...

We were once beta-testing a new Fortran compiler from IBM, when it failed to compile some perfectly legal (and simple) code with the fatal error message THAT USELESS ****** DAVE HASN'T WRITTEN THIS BIT YET.

The best part of the joke was not the message, but IBM's over-reaction when we sent back the formal error report!
 
  • #10
Borek said:
Have you ever used expletives in your code? Like printf("An **** programmer wrote it.\n") or puts("*** again?"); ?

I was working on a project (for strictly internal use, so presentability was irrelevant) with someone whose job it was to write a java application that used sockets, and we were running into issues with regards to the computer correctly releasing (not sure if this is the technical term, he was there to be the guy who knows what a socket is) the socket when we were done using it. We were never able to fix all the issues, and by the end of it our official error message scheme that we documented was broken down into the number of times the words "****ing socket" was used.
 
  • #11
Not profanity, but related:

I was working on a project that involved an amine that was a fine powder and smelled soooooo fishy. In the report I submitted to my boss, I referred to this compound as "powdered cat breath":

The resins were catalyzed with powdered cat breath at the following application rates...

I thought she would be amused - she had a good sense of humor!

Well the final report was sent to the home office in Finland, and a good part of it was the report I wrote, cut and pasted *without edits*. I don't know if it was an oversight or if she just didn't read what I wrote, but I'm sure some poor Finnish chemist was left wondering, "powdered cat breath"...wth??
 
  • #12
Office_Shredder said:
I once did a research project where I was instructed to keep detailed notes on my work in a notebook. The writing style was... let's call it casual. At the end the professor in charge informed me that the grant required that I turn the notebook over in case anybody wanted to audit the work I did during the project. It is now in the possession of the federal government.

What does it mean for someone to audit your research? Like they'll go through it and look for stuff you did wrong?

If so, that seems like a really crappy way to treat somebody...
 
  • #13
Well when you're using public money to write things notebooks, the public deserves to see what you wrote.

The only place I've experienced it is in vertebrate animal research labs, where there are ethics considerations. I've never seen it in theoretical research.
 
Last edited:
  • #14
dipole said:
What does it mean for someone to audit your research? Like they'll go through it and look for stuff you did wrong?

If so, that seems like a really crappy way to treat somebody...

My understanding was basically if someone accused the professor of wasting the grant money, they could simply check the notebooks to see if research was actually being done.
 
  • #15
Office_Shredder said:
My understanding was basically if someone accused the professor of wasting the grant money, they could simply check the notebooks to see if research was actually being done.

That's possible, but I really only see it in experimental labs. We still use federal money in computational/theoretical pursuits. Of course, they're allowed to confiscate our computers... but then you're relying on being able to understand scatter-brained code without proper annotaiton :bugeye:

(I guess that's really no different than scatterbrained notebooks with bad handwriting though...)
 
  • #16
lisab said:
Not profanity, but related:

I was working on a project that involved an amine that was a fine powder and smelled soooooo fishy. In the report I submitted to my boss, I referred to this compound as "powdered cat breath":



I thought she would be amused - she had a good sense of humor!

Well the final report was sent to the home office in Finland, and a good part of it was the report I wrote, cut and pasted *without edits*. I don't know if it was an oversight or if she just didn't read what I wrote, but I'm sure some poor Finnish chemist was left wondering, "powdered cat breath"...wth??
:smile:
 
  • #17
I guess it's OK as long as you can deliver.
 
  • #18
phion said:
I guess it's OK as long as you can deliver.

And warranted when you can't.
 
  • #19
"Powdered cat breath" sounds like a machine translation.
 
  • #20
Borek said:
"Powdered cat breath" sounds like a machine translation.

I was thinking more Gleipnir from norse mythos...
The dwarves fashioned the chain out of six supposedly impossible things:
The sound of a cat's footfall
The beard of a woman
The roots of a mountain
The sinews of a bear
The breath of a fish
The spittle of a bird
Went a bit wrong on the beard thing...
 
  • #21
dipole said:
What does it mean for someone to audit your research? Like they'll go through it and look for stuff you did wrong?

If they were auditing against some recognized standard (e.g. ISO9001), not so much looking for "stuff you did wrong", but looking to see it the research team as a whole had some some procedures to check for "stuff that was done wrong", and that they actually followed those procedures and fixed the mistakes.

Making mistakes isn't a big deal, but not having any evidence that you checked for any mistakes might be a very big deal, especially if your research leads to people getting killed.
 

Similar threads

  • · Replies 2 ·
Replies
2
Views
2K
  • · Replies 8 ·
Replies
8
Views
2K
Replies
7
Views
2K
  • · Replies 10 ·
Replies
10
Views
3K
  • · Replies 7 ·
Replies
7
Views
2K
  • · Replies 4 ·
Replies
4
Views
1K
  • · Replies 12 ·
Replies
12
Views
5K
  • · Replies 5 ·
Replies
5
Views
2K
  • · Replies 93 ·
4
Replies
93
Views
14K
Replies
4
Views
1K