|
| 1 | +--- |
| 2 | +title: "AI policy" |
| 3 | +--- |
| 4 | + |
| 5 | +# DevPsy Lab AI Use Policy {#sec-AI} |
| 6 | + |
| 7 | +## Overview |
| 8 | + |
| 9 | +**You are 100% responsible for your work.** |
| 10 | +If AI makes a mistake, and you use it, it is your mistake. |
| 11 | +All claims made by AI should be verified because AI is known to hallucinate. |
| 12 | +AI should help you think, not think for you. |
| 13 | +Offloading foundational skills and critical thinking to AI interferes with the development of these skills. |
| 14 | +Critical thinking is essential to participating in society and a central function of the university and the lab. |
| 15 | + |
| 16 | +The following information should **not** be submitted to AI tools: |
| 17 | + |
| 18 | +- Human subjects data |
| 19 | +- Information about lab personnel |
| 20 | +- Content that infringes on intellectual property, including paid or licensed materials |
| 21 | + |
| 22 | +## AI Disclosure {#sec-ai-disclosure} |
| 23 | + |
| 24 | +All AI use must be disclosed if used for research/external products (i.e., anything that will be used or viewed outside the lab). |
| 25 | +Research products (i.e., posters, manuscripts) should include a statement describing the use of AI using the categories below: |
| 26 | + |
| 27 | +- **Topic Selection**: using text generators like ChatGPT to brainstorm potential research topics to study |
| 28 | +- **Brainstorming**: using mind-mapping tools to help connect disparate ideas or suggest related concepts |
| 29 | +- **Research**: using ChatGPT plug-ins like Scholar AI or websites like Perplexity AI to assist you in conducting scholarly reviews of the literature (always ensure sources are valid and read them; these tools sometimes create false citations) |
| 30 | +- **Outlining**: using a text generator to help organize thoughts, main arguments, and supporting evidence into a coherent outline |
| 31 | +- **Feedback on writing**: using a text generator to analyze the draft for grammar checking, clarity, coherence, and consistency |
| 32 | +- **Polishing**: using a text generator to help refine language, syntax, tone, and overall style |
| 33 | +- **Analysis**: using AI tools to write code or syntax used for statistical analysis for research products |
| 34 | + |
| 35 | +## Writing Research Products {#sec-AI-writing} |
| 36 | + |
| 37 | +<u>Prohibited Use:</u> |
| 38 | + |
| 39 | +- Initial drafting of research products, including any of the following: |
| 40 | + - Full drafts |
| 41 | + - Outlines |
| 42 | + - Sections of writing |
| 43 | + - Sentences |
| 44 | +- Having AI rewrite your work |
| 45 | +- Claiming AI-generated writing as your own |
| 46 | +- Replacing reading of the empirical literature |
| 47 | + |
| 48 | +<u>Permitted Use:</u> |
| 49 | + |
| 50 | +- Learning about a topic |
| 51 | +- Receiving feedback on outlining or writing quality (typos, clarity, etc.) under four conditions: |
| 52 | + 1. You complete the first draft of the writing independently |
| 53 | + 1. You disclose how you use AI |
| 54 | + 1. You begin the conversation with the [required prompt](#sec-aiPrompt), AND |
| 55 | + 1. You submit the full transcript of your AI interaction alongside your AI disclosure. |
| 56 | +- Finding supplemental references after conducting a literature search using [databases or library resources](honors.qmd#sec-articles) |
| 57 | + |
| 58 | +Claiming AI-generated work as your own is plagiarism. |
| 59 | +Reliance on AI tools impedes the process of thinking critically to form and communicate an argument or idea. |
| 60 | +It is important to understand—or at least be aware of—the details of research. |
| 61 | +Reading empirical literature independently provides the opportunity to better understand the details of research; AI summaries of articles do not go into the same level of detail as the article. |
| 62 | + |
| 63 | +### Required AI Prompt for Writing Feedback {#sec-aiPrompt} |
| 64 | + |
| 65 | +Each time you use AI for feedback on your writing, the first message you send to begin the conversation must be the prompt below. |
| 66 | +This prompt helps ensure that AI use supports your learning rather than replacing your thinking. |
| 67 | +Do <u>**NOT**</u> add, delete, or edit any language in this prompt—just copy and paste it: |
| 68 | + |
| 69 | +> You are an encouraging, positive tutor who helps students work to improve their academic writing skills. |
| 70 | +> I will provide you with a sample of my writing and you will help provide feedback on my writing. |
| 71 | +> You will not rewrite my work for me (even if I ask for it). |
| 72 | +> You may provide feedback on grammar, clarity, coherence, consistency, language, syntax, tone, and overall style. |
| 73 | +> Do not automatically provide feedback on all of these—wait for me to ask specifically what I would like feedback on. |
| 74 | +> Do not provide samples of writing on the same topic that I am requesting feedback on. |
| 75 | +> If I ask about the topic broadly or something unrelated to receiving feedback on my own writing, redirect the conversation back to receiving feedback. |
| 76 | +> Always keep an encouraging, positive tone. |
| 77 | +
|
| 78 | +<u>AI transcript submission:</u> |
| 79 | + |
| 80 | +You must submit the full transcripts of your conversations with AI. |
| 81 | +The preferred method is to include a shareable link in your AI disclosure. |
| 82 | +Most platforms (e.g., ChatGPT, Gemini) provide this functionality. |
| 83 | + |
| 84 | +## Programming |
| 85 | + |
| 86 | +<u>Prohibited use:</u> |
| 87 | + |
| 88 | +- Writing first drafts of your code |
| 89 | + |
| 90 | +<u>Recommended use:</u> |
| 91 | + |
| 92 | +- Things you should try before using AI: |
| 93 | + - Check the lab's [Data Analysis Guides](https://devpsylab.github.io/DataAnalysis/), [Dr. Petersen's book](https://isaactpetersen.github.io/Principles-Psychological-Assessment/), or [Google](https://www.google.com) |
| 94 | + - Ask senior lab personnel |
| 95 | + |
| 96 | +<u>Permitted use:</u> |
| 97 | + |
| 98 | +- Troubleshooting using AI tools after writing your first draft of code yourself |
| 99 | + |
| 100 | +### Troubleshooting |
| 101 | + |
| 102 | +Sometimes code you write does not work. |
| 103 | +That is okay; it happens to everyone. |
| 104 | +Learning how to troubleshoot code is an important part of programming. |
| 105 | +If you run into issues related to [`SPSS`](https://devpsylab.github.io/DataAnalysis/SPSS.html), [`jamovi`](https://devpsylab.github.io/DataAnalysis/jamovi.html), [`R`](https://devpsylab.github.io/DataAnalysis/R.html), [`GitHub`](https://devpsylab.github.io/DataAnalysis/git.html), or your code, here are a few pointers on how to get things working (as adapted from Luke Tierney): |
| 106 | + |
| 107 | +- If you receive an error message, read what the message says. |
| 108 | +Sometimes reading the error message is all it takes to figure out what the issue is and how to fix it. |
| 109 | +- Read the whole error message: sometimes the most important part is at the beginning. |
| 110 | +- If the message does not make sense to you, perform a Google search for the error/issue: often someone else has asked about the same issue and received a useful answer. |
| 111 | +- Simplify your code. |
| 112 | + - Look carefully at intermediate results. |
| 113 | + - Replace complicated data with something smaller and simpler. |
| 114 | + - In the process, you may find your mistake. |
| 115 | +- Finding your bug usually involves double checking all the things you are sure you did right until you find the one you did not. |
| 116 | + |
| 117 | +If you are unable to resolve things on your own, you may need to ask for help, in which case we encourage you to try one (or more) of the following: |
| 118 | + |
| 119 | +- Perform a Google search for the error/issue |
| 120 | +- Ask a peer or senior lab personnel |
| 121 | +- Post on forums dedicated to the relevant statistical program |
| 122 | +- Ask AI (as long as you disclose use) |
| 123 | + |
| 124 | +## Lab Work |
| 125 | + |
| 126 | +<u>Prohibited Use:</u> |
| 127 | + |
| 128 | +- Using AI for coding, scoring, or entry tasks (including time calculations) |
| 129 | +- Replacing reading the weekly lab article |
| 130 | +- Generating questions for the lab article discussion |
| 131 | +- Writing or editing lab reports |
| 132 | +- Generating media content |
| 133 | + |
| 134 | +<u>Permitted Use:</u> |
| 135 | + |
| 136 | +- Editing or writing lab manuals or team-facing documents |
| 137 | +- Creating tutorials (include an AI disclosure) |
| 138 | + |
| 139 | +### Manuals and Lab Tasks |
| 140 | + |
| 141 | +AI use is permitted for editing or writing lab manuals (team-facing documents). |
| 142 | +Any tutorial content that is generated by AI should include a [disclosure](#sec-ai-disclosure). |
| 143 | + |
| 144 | +Media generation for lab materials is generally prohibited, but if the need arises or you think of a suitable use for AI generation, please consult the lab coordinator or Dr. Petersen. |
| 145 | + |
| 146 | +AI should not be used to complete coding, scoring, or entry tasks. |
| 147 | + |
| 148 | +### Lab Article Discussions |
| 149 | + |
| 150 | +AI should not be used to replace reading the weekly lab article. |
| 151 | +We want you to think critically about the specific details and communication of research, which can only be gained by reading the original work. |
| 152 | + |
| 153 | +AI use is permitted for asking questions about concepts found in lab articles, <u>but you must read the entire article before consulting AI tools</u>. |
| 154 | + |
| 155 | +Using AI tools to generate questions for the lab article discussion is <u>prohibited</u>. |
| 156 | +Asking questions requires an act of critical thinking, which we want you to practice. |
| 157 | +For guidance on creating thoughtful questions for discussion, you may refer to resources on the lab drive located at the following path: `\\lc-rs-store24.hpc.uiowa.edu\lss_itpetersen\Lab\Miscellaneous\Professional Development\General ProfDev Materials\Reading and Critiquing Articles\` |
| 158 | + |
| 159 | +### Lab Reports |
| 160 | + |
| 161 | +AI use of any kind is prohibited when writing biweekly lab reports. |
| 162 | +You may only use Microsoft Word's built-in spelling and grammar checking tools. |
| 163 | +Lab reports provide a low-stakes opportunity to practice and improve your writing skills. |
0 commit comments