Policies
Workload expectations
This is a 1-credit hour course, so you should expect to complete ~ 30-40 hours of work for the course, or about 4 hours each week (this includes time in-class).
My estimate for time usage for activities and assignments in an average week is below – some weeks may have shorter or longer time commitments either by design or due to course scheduling.
Activity Hours per Week In-class meetings ~1.5 hours Informal exercises 0.5 Homework assignments 1.0 Research, drafting, editing for final project 1 TOTAL 4
Communication
Electronic
- Our class will communicate through our Canvas site. Announcements and emails are archived there, automatically forwarded to your UO email, and can even reach you by text. Check and adjust your settings under Account > Notifications.
- We will also be using this GitHub Pages website (https://wcresko.github.io/BioE_Comp_Tools_Fa2026/) for the course as the repository for lecture schedule, syllabus, lecture slides and other materials.
- Every Monday I will post an Announcement that previews critical concepts we’ll work on that week and a checklist of the week’s due dates.
- I will contact individual students when needed through email, and I try to respond to questions within one business day.
- When giving feedback on assignments, I do so in Canvas, and turnaround time for feedback is generally one week.
Office hours
- I will host office hours each week on Friday from 11:00 to 12:00 in the KC2 Computational Suite. The end of many class periods will also function as a form of office hour.
- I welcome meetings outside my regular office hours as well - please email me to set a time.
- During office hours, students bring in a wide range of concerns, questions, and successes. We might
- talk through a specific concept or problem to clarify it
- think together about an issue a student is curious about that relates to the class
- discuss a student’s post-graduation goals
- identify more supportive methods to study for a future exam or to begin a project
- or any number of other topics
Classroom Community Expectations
Participate and Contribute:
All students are expected to participate by sharing ideas and contributing to the learning environment. This entails preparing, following instructions, and engaging respectfully and thoughtfully with others. While all students should participate, participation is not just talking, and a range of participation activities support learning. Participation might look like speaking aloud in the full class and in small groups, and working collaboratively on coding projects. We will establish more specific participation guidelines and criteria for contributions in our first weeks of the term.
Expect and Respect Diversity
All classes at the University of Oregon welcome and respect diverse experiences, perspectives, and approaches. What is not welcome are behaviors or contributions that undermine, demean, or marginalize others based on race, ethnicity, gender, sex, age, sexual orientation, religion, ability, or socioeconomic status. We will value differences and communicate disagreements with respect. We may establish more specific guidelines and protocols to ensure inclusion and equity for all members of our learning community.
Help Everyone Learn
Part of how we learn together is by learning from one another. To do this effectively, we need to be patient with each other, identify ways we can assist others, and be open-minded to receiving help and feedback from others. Don’t hesitate to contact me to ask for assistance or offer suggestions that might help us learn better.
Generative Artificial Intelligence (GenAI) Use
Generative AI tools (ChatGPT, Claude, Gemini, GitHub Copilot, and the AI assistants built into Positron and VS Code) are part of modern computational work, and learning to use them well - and to recognize when they are wrong - is a goal of this course (Week 9). In this class you may use GenAI as a process aid: to explain an error message, suggest how a command or function works, sketch an approach, or help you debug code you have written. You may not submit GenAI content as your own: every line of code, prose, and every figure you turn in must be something you wrote, understood, and can explain, and you must be able to run it yourself. If you do use a GenAI tool for any part of an assignment, add a brief note saying which tool you used and for what (e.g., “asked Copilot to explain the awk syntax in step 3”); undisclosed use, or submitting generated work as your own, is academic misconduct under the Student Conduct Code and will be reported to the Office of Student Conduct and Community Standards. Because these tools keep what you paste into them, never paste unpublished lab data, protected data (human subjects, HIPAA, FERPA), or anything covered by a data-use agreement; UO’s GenAI data-privacy guidance explains what is and is not safe. This policy follows UO’s guidance on GenAI in courses (“GenAI use allowed with specific limitations”); if you are unsure whether a particular use is okay, ask me first.
University Course Policies
Please read and make sure you are familiar with the important policies that apply to all UO courses, which can be found here.