Network Analytics

Semester: Summer-2026

Course number: DSAN-6400

Course description

The design and analysis of networks to represent interactions between and within data is a quickly emerging discipline of significant importance. Data Analytics combines graph theory, optimization, data science, data visualization, community and cluster analysis, and more. Topics in this course will help answer intriguing questions such as, “How can we make sense of large, highly-associated data sets, ranging from social networks to the smart power grid?” or “Which models are more accurate for predicting popularity on Twitter?” or “How can we estimate the spread of a contagion or of information?” The course will begin with a discussion of applications, specifically to data science and analytics. From there, a formal framework for analysis of graphs and trees will be introduced. This will include graph theory and representation, optimization, and graph-based algorithms. Next packages in Python and/or R will be investigated for the purposes of exploring and visualizing data that contain relationships. These packages will then be used to model and analyze complex data sets for the purposes of community detection, path analysis, influencer assessment, logistics analytics, contagion or information spread (such as rumor spreading), web page ranking, and more. Examples of data science applications are provided with real-world data sets including social network data, web-based data, attributed data, flow data, biological data, and more. 3 credits

Course details

Instructional team

The following are the email addresses for the instructional team.

Professors

• Professor James Hickman: webpage

Teaching assistants

• Yuhua Pang \(\rightarrow\) yp310@georgetown.edu

Canvas

Most of the content for the course will be hosted on this website. However, Canvas will also be used for deliverable submissions, grading, quizzes, and due dates.

The Canvas site for the class can be found at the following link: Canvas page

Textbooks

Primary textbook:
• Filippo Menczer, Santo Fortunato and Clayton A. Davis A First Course in network science, Cambridge University Press, 2020

Note: This book can be found online and on Amazon, however, the textbook is optional. We will be following the book closely, so most of the content in the book will be covered in the lectures and labs.

Additional textbooks:
• Network Science by Albert-László Barabási
• A User’s Guide to Network Analysis in R (2015, Springer):

Shared folder

In the navigation bar, and at the link below, is a link that will take you to a cloud-based Google Drive shared directory (folder) with various sub-folders such as “labs”, “recordings”, “homeworks”, etc.

https://drive.google.com/open?id=1CzO7PAB19OZ4cERglVsTJHWP0ITwGMAs&usp=drive_fs

New content and slides will be periodically added to the folders as the semester progresses.

If something appears to be missing then notify your professor ASAP!

Course structure

The following is the typical format for most DSAN courses, however, professors may choose to deviate from this format.

Lectures (1.5 hr)

  • Each week will contain a 1.5-hour lecture, followed by a 1-hour lab period.
  • The lecture covers a large amount of information with Q&A at the end (~10 minutes):

Lab (1.0 hr)

  • General Q & A (~10 minutes)
  • Hands-on coding demonstration and assignment (.ipynb or .rmd) (~40 minutes):
  • Student presentations (when applicable)+Q&A: (~10-15 minute)

Outside of class

  • This is a graduate level class, you should expect to spend around 10 to 20 hours on it per week outside of class.

Meeting times

Please refer to the calendar tab for this information: (click here for calendar)

AI tool usage

See the following PDF for departmental guidelines on AI tool usage.

DSAN AI tool usage guidelines PDF

Topics and Timeline

IMPORTANT: This is a tentative timeline and maybe subject to changes

Week-01: Foundations of Modern Networks

  • Course overview and modern network applications
  • Graph representations and network types
  • Introductory visualization and analysis tools
  • NetworkX and graph analytics ecosystem

Week-02: Structure, Connectivity, and Small Worlds

  • Paths, distances, clustering, and connectedness
  • Homophily, assortativity, and small-world structure
  • Structural properties of real-world networks
  • Temporal connectivity concepts

Week-03: Centrality, Hubs, and Robustness

  • Centrality measures and influence metrics
  • Scale-free and heavy-tailed networks
  • Core decomposition and resilience
  • Cascading failures and adversarial robustness
  • Modern graph visualization workflows

Week-04: Directed, Weighted, and Heterogeneous Networks

  • Directed and weighted graph analysis
  • Spectral methods and PageRank
  • Knowledge graphs and heterogeneous networks
  • Graph databases and graph querying

Week-05: Communities, Embeddings, and Representation Learning

  • Community detection and modularity
  • Spectral clustering and hierarchical methods
  • Graph embeddings and representation learning
  • Node2Vec, DeepWalk, and contrastive learning
  • Embedding evaluation and benchmarking

Week-06: Deep Learning for Graphs

  • PyTorch and PyTorch Geometric fundamentals
  • Message passing neural networks
  • Graph convolutional networks (GCNs)
  • GraphSAGE and inductive learning
  • Scalable graph training workflows

Week-07: Advanced Graph Neural Networks I

  • Graph attention networks (GATs)
  • Graph transformers
  • Transformer-style message passing
  • Positional and structural encodings
  • Self-supervised graph learning

Week-08: Advanced Graph Neural Networks II

  • Temporal graph neural networks
  • Heterogeneous and relational GNNs
  • Hypergraphs and higher-order networks
  • Geometric deep learning
  • Foundation graph models and graph reasoning
  • LLM + graph integration

Week-09: Dynamic Networks, Diffusion, and Simulation

  • Temporal and evolving graph systems
  • Epidemic spreading and contagion
  • Influence propagation and diffusion dynamics
  • Agent-based simulation on networks
  • Dynamic visualization and simulation workflows

Week-10: Graph AI Systems and Emerging Applications

  • Knowledge graph reasoning
  • Recommender systems and anomaly detection
  • Scientific machine learning with graphs
  • Cybersecurity and infrastructure applications
  • Multi-agent systems and networked AI
  • Distributed and large-scale graph learning

Week-11: Network Optimization and Decision Intelligence

  • Shortest paths, flows, cuts, and spanning structures
  • Routing, scheduling, and resource allocation
  • Convex and combinatorial optimization on graphs
  • Graph reinforcement learning
  • Robust and stochastic network optimization
  • Digital twins and real-time decision systems

Week-12: Capstone Project Presentations

  • Research or application-focused graph AI projects
  • Simulation and optimization demonstrations
  • Benchmarking and evaluation
  • Future directions in network science and graph intelligence

Grading

Point system

Your grade will be determined using a simple points system. Points will be allocated based on performance and/or completion of course deliverables (see the following section). Each deliverable will earn you a specified number of points. At the end of the semester, there will be some final number of total possible points, typically around 1000 total points. Your final grade will be computed using the following formula.

GRADE PERCENTAGE = 100*POINTS_EARNED/TOTAL_POINTS_POSSIBLE

Where the letter grade is computed using the following rules:

  • A : >= 92.5%
  • A- : 89.5 - 92.49%
  • B+ : 87.99 - 89.49%
  • B : 81.5 - 87.98%
  • B- : 79.5 - 81.49%
  • C : 70 - 79.49%
  • F : 70% or less

NOTE: Unless otherwise stated, for group deliverables, all students will receive the SAME grade (except for points associated with individual a peer-evaluations)

Expectations

Many of the assignments in this class are open-ended. This means that there are dozens of ways to successfully complete the assignment. In general, submitting a deliverable will not automatically give you an “A”. In this class grading is typically holistic, meaning that there will not always be specific point values for individual elements of a deliverable. Each deliverable submission is unique and will be compared to all other submissions. The method of holistic grading looks at the entire submission as a whole. It looks at effort, creativity, meeting and exceeding requirements, writing and communication skills, ease of review, clarity, etc. Therefore, if your work is “good”, but could be better, your grade will reflect this.

If your submission meets or exceeds the requirements, is creative, is well thought-out, demonstrates critical thinking and serious effort, has proper publication quality visualizations and grammar, and is at the graduate student level, then you can expect a high score.

Grade brackets

Typically, we will compute grades based on the extent to which the quality of your work falls into the following brackets.

  • Excellent: A (100%) The deliverable component was taken very seriously, correctly completed, done professionally, and appears to exceed all expectations.
  • Good: A- (90%) The deliverable component was seriously attempted, meets expectations, and does not have any missing components. However, there are a few issues that need minor improvement.
  • Acceptable: B (80%) The deliverable component was attempted and mostly meets expectations. However, there are some minor missing requirements, or parts that are incorrect and require moderate improvement.
  • Needs improvement: C (70%) The deliverable component was attempted but is below expectations. Several parts are incorrect and need significant improvements, or show some lack of effort.
  • Needs serious improvement: D (60%) The deliverable component was attempted but is significantly below expectations. It has many serious issues, several missing components, or obvious lack of effort.
  • Unacceptable: (0%) The deliverable component was not attempted, or is largely blank, or is otherwise somehow unacceptable.

Grader summary

Professors may deviate from this, however, typically the following individuals will be responsible for grading the respective deliverables

  • Professors
    • Project deliverables
    • Lab presentations
  • TAs
    • Lab assignments
    • Discussions
    • Open ended quiz and exam questions
    • Homeworks
  • Canvas automatic grading
    • Non-open ended quiz and exam questions (e.g. true/false, multiple choice, etc)

Deliverables

Definition: A deliverable is anything that you turn in for a grade.

Due dates

  • Due dates in this class will typically be at 11:59PM (EST) on Tuesday or Wednesday. However, this may vary due to holidays and when the assignment was made available.
  • Due dates will never fall on weekends or holidays.
  • The official due dates for this class can be found in two locations.
    • On each assignment’s associated Canvas page
    • On the following Canvas page (click here).

Point breakdown

The percentages below are approximate and may vary slightly. For example, the total final points value may deviate from 1000, particularly if deliverables are cancelled or made optional bonus assignments.

  • Project: 200 points
    • Project: Mid-point presentation and discussion: 25 pts
    • Project: Final presentation: 50 pts
    • Project: Paper: 75 pts
    • Project: Code and live technical evaluation: 50 pts
  • Virtual Journal Club: 60 points
    • Virtual journal club presentation: 50 pts
    • Virtual journal club attendance 1: 10 pts
  • Homeworks: 350 poitns
    • 5X, 70 pts each
  • Technical Proficiency Evaluation (Verbal Coding Assessment)(1X): 140 point
  • Lecture attendance and participation: 50 points
  • Handwritten Quizzes: 200 points
    • (5x, 40 points each)
  • Total: 200+60+350+140+50+200=1000 points

Project

See the Project pages in Canvas for more information on this deliverable:

Virtual Journal Club

See the Virtual Journal Club pages in Canvas for more information on this deliverable:

Technical Proficiency Evaluation (Verbal Coding Assessment)

Late in the semester, each student will complete an individual Technical Proficiency Evaluation conducted remotely via Zoom. Students will be responsible for scheduling a meeting time with the instructor during the designated evaluation window. This assessment is designed to evaluate the student’s practical understanding of the course material, technical reasoning ability, coding proficiency, and ability to communicate technical concepts clearly and accurately.

The evaluation will be similar in spirit to a professional technical interview and may include a combination of the following:

  • Verbal technical questioning covering major course concepts, methods, and terminology
  • Live problem solving and algorithmic reasoning
  • Interpretation and discussion of code snippets, outputs, or debugging scenarios
  • Short live coding demonstrations or walkthroughs
  • Discussion of design decisions, tradeoffs, assumptions, and implementation strategies
  • Questions connecting theoretical concepts to practical applications

Students may be asked to explain both previously completed coursework and novel problems that require transferring and applying concepts learned throughout the semester. The emphasis will be placed not only on arriving at correct answers, but also on demonstrating clear technical reasoning, structured problem-solving approaches, and fluency with the computational tools and methodologies used in the course.

A study guide outlining the general scope and expectations of the evaluation will be provided later in the semester to help students prepare appropriately.

This evaluation is intended to assess individual mastery of the material and to verify technical competency in an interactive setting. Students are expected to participate with functioning audio, video, screen-sharing capability, and access to an appropriate coding environment if requested.

To preserve the integrity of the assessment, students are expected to answer questions independently without the use of unauthorized external assistance, including AI systems, hidden notes, or off-screen prompting. If, during the evaluation, it is believed that a student may be reading responses from a screen or using unauthorized AI assistance, the instructor reserves the right to require that subsequent questions be answered with the student’s eyes closed or while visibly looking away from the screen for the remainder of the assessment.

Additional details regarding scheduling procedures, evaluation format, allowed resources, duration, and grading criteria will be provided later in the semester.

Lecture attendance and participation

See the Lecture attendance and participation pages in Canvas for more information on this deliverable:

Quizzes

Approximately every two weeks, students will complete a take-home handwritten quiz designed to reinforce and assess understanding of the course material. These quizzes will consist of a variety of analytical and conceptual exercises aligned with recent lecture content, readings, and assigned coursework.

Quiz content may include, but is not limited to:

  • Mathematical derivations and analytical problem solving
  • Applied computational or quantitative exercises
  • Theoretical and conceptual short-answer questions
  • Interpretation of models, algorithms, or experimental results
  • Diagram construction, labeling, and technical illustrations
  • Explanations of methodology, assumptions, and reasoning processes
  • Multi-step problems requiring intermediate work and justification

The purpose of these quizzes is to evaluate individual comprehension, technical communication, and the ability to reason through problems in a structured and methodical manner. Students are expected to clearly show all relevant work, derivation steps, assumptions, and supporting explanations where appropriate. Final answers without sufficient supporting work may receive reduced credit.

Due to excessive AI-assisted submissions observed in prior coursework, all quiz submissions must be completed entirely by hand. Acceptable submission formats include:

  • Handwritten work on paper submitted as clear photographs or scanned PDF documents
  • Handwritten digital submissions completed using a tablet device and stylus (e.g., iPad with Apple Pencil)

Typed submissions of any kind are not permitted for these assessments. This includes plain-text responses, word-processed documents, AI-generated content, and LaTeX-formatted submissions. Any non-handwritten submission will be considered non-compliant with the assignment requirements and will receive a grade of zero.

Students are responsible for ensuring that all submitted pages are legible, properly ordered, and fully uploaded before the deadline. Illegible, incomplete, corrupted, or improperly uploaded submissions may not be eligible for grading. Additional submission instructions, formatting expectations, and quiz policies will be provided throughout the semester.

Homeworks

  • DESCRIPTION: Every two weeks there will be a homework (HW) which you will have two weeks to complete.
  • SUBMISSION AND GRADING: More details will be included on each HW’s assignment’s webpage with submission and grading details.
  • GRADING: Homeworks will be graded using assignment specific rubrics.

Late penalties

All due dates are specified in Canvas at the following link click here

General Recommendation

Due dates are when the deliverable MUST be completed by, NOT when they SHOULD be completed by. You should get things done well before the due date. DO NOT WAIT UNTIL THE LAST MINUTE TO COMPLETE DELIVERABLES. Proper time management will be extremely important in your future careers, the same is true in the DSAN program!

Also, do not expect urgent help on something at the last minute. For example, do not expect prompt responses from TAs or Instructors at 7PM for an assignment that is due at 11:59PM.

Quizzes, discussions, and presentations

  • IMPORTANT: Quizzes, discussions, and presentations are time-sensitive and therefore CAN’T be late. There is no grace period. Failure to submit will result in zero points allocated if not done at the appropriate time

Everything else

For all other deliverables, late penalties for submissions past the Canvas deadline obey the following rules;

  • 0 to 24 hours late: 0% deduction (grace period)
  • 24 to 48 hours late: 5% deduction
  • 48 to 96 hours late: 10% deduction
  • 96 to 120 hours late: 20% deduction
  • 120 or more hours late: 30% deduction]
  • Important: You can submit these deliverables late any time during the semester. However, you will receive a maximum of 70% for the submission. The deliverable will be graded as usual on top of the 30% deduction.

Extensions

We’ve allowed extensions in the past and they were problematic, causing students to fall behind. Because of this, we are not granting extensions for assignments.

We know that “life happens”, to accommodate this we are instead using very lenient submission policies, including:

    1. Long submission windows to complete the assignments (e.g. a week for a lab assignment)
    1. Provided a generous grace period after the due date.
    1. Long late windows with lax late penalties
    1. Ability to submit anything, anytime in the semester, for up to 70% credit.

DO NOT EMAIL US TO ASK FOR EXTENSIONS, THERE ARE NO EXTENSIONS FOR THIS CLASS

This is a large class and we can’t accommodate edge cases, giving one student an extension means that we need to give the option for extensions to all students, which is logistically infeasible.

Obviously there are highly rare and extreme life events, such as breaking a bone, giving birth, losing a finger, serious car-accidents, and deaths in the family, in such cases, reach out to the professor and explain the situation. Colds, Flu, lack of planning, and other common illness do not meet the criteria for “extreme life events”. If you are worried about getting sick, start the assignment early before you get ill.

Office hours

Office hours with TAs and Professors are available at various times. The scheduling links to set up office hours with the instructional team can be found in the Office hours tab at the following link.

Click here to set up office hours

  • Unless requested otherwise, office hours will be virtual using video conferencing.
  • If you want to discuss code during the office hours, please email a copy of the code to the TA or Professor before the meeting.

Getting help

The instructional team wants everyone to succeed!

If you are struggling in this class, do not try to “go it alone”, reach out for help ASAP!

The following are recommendations for students struggling in the class.

Recommendations

  1. Form study groups: Start reaching out to classmates in the class to form study groups.
  2. Attend office hours: Start attending office hours with TAs and professors for extra help
  3. Stay active on Google-Spaces:
    1. Google-Spaces is a place meant for you to reach out quickly and ask questions, please make sure you are using this resource.
    2. Also, there are various clarifications about the deliverables.
    3. If you have a question, you are probably not the only one who does.
    4. Make sure you are keeping up to date on the Google-Spaces conversations
  4. Use the code we provide: Make sure you are familiarizing yourself with the codes and other content provided by the instructional team
  5. Re-watch the lectures: All lectures are recorded and shared with the class. Make sure to re-watch if there are points that are confusing.
  6. Review bootcamp material: If you need extra help with R or python fundamentals then please review the bootcamp materials (see below for link).
  7. Reach out to the ARC program: The Academic Resource Center (ARC) is the campus office responsible for reviewing medical documentation and determining reasonable accommodations to students with disabilities.

Public communication

The primary way in which the instructional team will address questions in this class is via Google-Spaces (or a similar software tool). All students MUST join the Google-Spaces workspace. The invitation can be found at the link below.

The following communication and collaboration is allowed in Google-Spaces

  • The discussion of ideas and approaches to problems
  • The discussion and resolution of any technical/code issue
  • Posting/sharing smal code snippets (up to a few lines) for very specific questions

You can run Google-Spaces through your browser, Android or iPhone.

  • WARNING: Google-Spaces is a public forum, all communications there MUST be academically and professionally acceptable. Avoid any disrespectful, violent, graphic, sexual, hateful, politically biased, or otherwise un-professional content. Failure to do so will result in disciplinary actions. Please use common sense by keeping everything appropriate and academically relevant, if in doubt, reach out to the professor before sharing content.

Join the Google-Spaces using the following invitation link

https://chat.google.com/room/AAQABm2EenU?cls=4

IMPORTANT: Google-Spaces is not an on demand “call center” where you can expect instant responses to your questions. Depending when you ask questions, you can expect the following response times.

  • Questions posted M-F between 9AM-5PM (EST) \(\rightarrow\) Expect responses in 2-6 hours
  • Questions posted M-F past 5PM (EST) \(\rightarrow\) Expect responses sometime the next day
  • Questions posted weekend \(\rightarrow\) Expect responses on Monday

Generally we will not answer questions on Google-Spaces six hours before an assignment’s deadline.

DSAN writing center

The department’s Writing and Communications Center actively and individually supports all Data Science & Analytics students in the areas of writing skills, communication skills, and presentation skills.

This includes cover letter and resume assistance, improving interview skills, assistance with writing graduate-level papers, and assistance with giving excellent and clear presentations.

Faculty and staff also offer support via workshops on resumes, cover letters, interview skills, writing & communication methods, and presentation skills.

https://analytics.georgetown.edu/dsan-writing-center/

Bootcamp content

Students can still access the Summer bootcamp if needed for review of fundamental concepts. It is recommended that you bookmark this webpage for quick access. 2022 DSAN bootcamp:

The following link maybe useful for students that want to review basic mathematics, python, and R fundamentals

https://jfh.georgetown.domains/bootcamp/

  • Username = GU_student_1
  • Password = GU_student_1

Plagiarism

General guidelines

  • If an assignment is not a group assignment, then it is meant to be individual work.
    • Such assignments must be STRICTLY YOUR OWN WORK, NO COLLABORATION!
  • In the past, there have been issues with students sharing code files with others, which are then submitted by multiple students as unique individual submissions. This is totally unacceptable and will result in penalties to all students involved.
  • If you have referred to lecture codes or resources on the internet please specify the references.
  • All other deliverables must be your own as well.
  • The following collaboration and communication is allowed and encouraged in Canvas discussion Q&A boards, labs, and office hours
    • The discussion of ideas and approaches to problems
    • The discussion and resolution of any technical issue
    • Collaboration means that you can talk, communicate and discuss general approaches and strategies to solving problems between each other freely, since that is part of the learning process. This can happen on the Google-Spaces channel, in person or in online discussions.
    • If you are ever unsure - ask us! do not risk it!
  • You cannot share your actual work with others, even if it’s for “just a look” or to “help out”
    • If you share your work with a friend - you are both cheating.
    • If you copy another student’s discussion post in any way you will receive a zero for that discussion
  • We also realize that some problems are short enough that there is a finite way of coding them, so code between students may be similar. However, all code submissions will be checked against every other students’ code, and any high level of similarity between students will be investigated.
  • We are aware that a huge volume of code is available on the web to solve any number of problems. Unless we explicitly tell you not to use something the course’s policy is that you may make use of any online resources (e.g. StackOverflow) but you must explicitly cite where you obtained any code you directly use (or use as inspiration). Any recycled code that is discovered and is not explicitly cited will be treated as plagiarism and considered an Honor Code violation. On individual assignments, you may not directly share code with another student in this class, and on team assignments, you may not directly share code with another team in this class. You are welcome to discuss the problems together and ask for advice, but you may not send or make use of code from another team.

If you obey the following guidelines, then you will typically be "safe".

  • NEVER copy text verbatim from an external source without citation. (external = not your original work)
    • If you need to used text verbatim from an external source then (1) put the text in quotes (2) provide an in-line academic citation
  • NEVER take part, or all, of the code for an assignment directly from an online source (e.g. GitHub)
    • Your work should be ORIGINAL, if your code (or results) are too similar to an online project then you will be subject to disciplinary action.
  • ALWAYS CITE THE SOURCE:
    • If you use concepts, source code, data, ideas, equations, etc, from an external source, in a professional “write-up”, then provide an in-line academic citation.
    • If you use code from online, then provide the source URL as a comment in the code.
    • e.g. # Source: The code below is modified from INSERT_URL
    • Citations are not required for short trivial chunks of code, for example, if you need to google “how to do a for loop in python”, then you do not need to cite the for loop instructions.

Plagiarism definition

Plagiarism is the intentional or unintentional presentation of another person’s idea or product as one’s own. Plagiarism includes, but is not limited to the following: copying verbatim all or part of another’s written work; using phrases, charts, figures, illustrations, code, or mathematical/scientific solutions without citing the source; paraphrasing ideas, conclusions, or research without citing the source; and using all or part of a literary plot, poem, film, musical score, or other artistic product without attributing the work to the creator. Students can avoid unintentional plagiarism by following carefully accepted scholarly practices. Notes taken for papers and research projects should accurately record sources of material to be cited, quoted, paraphrased, or summarized, and papers should acknowledge these sources in footnotes.

For more information see: https://honorcouncil.georgetown.edu/whatisplagiarism/

Using external sources

Generally, you need to be careful about copying things word-for-word into a submission, even if a citation is provided.

The only exception to this would be direct quotes, which should be rare and only included if they are needed to strengthen the narrative.

Direct quote example: “the only thing we have to fear is fear itself.” (Franklin D. Roosevelt)

To be safe,

  1. Keep direct quotations to a minimum unless they are particularly important and are required to strengthen the narrative.

  2. It is okay to use information from external sources, but you shouldn’t copy it verbatim (word-for-word) directly, even if you provide a citation. Instead ingest and digest the material on your own, and then express it in your own words, as needed to build the narrative. This is always true for publication quality write-ups (published news articles, peer-reviewed articles, graduate project submissions, etc).

Penalties for plagiarism

All individual work is, by definition, INDIVIDUAL. We have a ZERO TOLERANCE POLICY for cheating and not doing individual work when required.

DO YOUR OWN WORK!!

If a deliverable looks too similar to another student’s, or to web resources, then you will have to explain yourself to the instructional team.

IF YOU CHEAT IN ANY WAY, THE FOLLOWING WILL HAPPEN

  • YOU WILL GET A ZERO FOR THE RELEVANT ASSIGNMENT.
  • YOU WILL BE REPORTED TO THE DSAN DEPARTMENT
  • YOU WILL BE REPORTED THE GEORGETOWN HONOR COUNCIL
    • Typically this will result in a line being added to your official-transcript, reporting that you have been caught cheating.
    • Repeated offenses can result in expulsion

Academic integrity

Academic integrity is central to the learning and teaching process. Students are expected to conduct themselves in a manner that will contribute to the maintenance of academic integrity by making all reasonable efforts to prevent the occurrence of academic dishonesty. Academic dishonesty includes (but is not limited to) obtaining or giving aid on an examination, having unauthorized prior knowledge of an examination, doing work for another student, and plagiarism of all types, including copying code.

As a Jesuit, Catholic university, committed to the education of the whole person, Georgetown expects all members of the academic community, students and faculty, to strive for excellence in scholarship and in character. The University spells out the specific minimum standards for academic integrity in its Honor Code, as well as the procedures to be followed if academic dishonesty is suspected. Over and above the honor code, in this course we will seek to create an engaged and passionate learning environment, characterized by respect and courtesy in both our discourse and our ways of paying attention to one another. source

All students are expected to maintain the highest standards of academic and personal integrity in pursuit of their education at Georgetown. Academic dishonesty in any form is a serious offense, and students found in violation are subject to academic penalties that include, but are not limited to, zero’ing out assignments, reduced grade, failure of the course, termination from the program, and revocation of degrees already conferred. All students are held to the Georgetown University Honor Code.

For more information about the Honor Code: Honor council

We have a ZERO TOLERANCE POLICY and if students are found to be in violation there will be consequences and the students will be penalized and reported.

Honor System

All students are expected to maintain the highest standards of academic and personal integrity in pursuit of their education at Georgetown. Academic dishonesty, including plagiarism, in any form is a serious offense, and students found in violation are subject to academic penalties that include, but are not limited to, failure of the course, termination from the program, and revocation of degrees already conferred. All students are held to the Georgetown University Honor Code. For more information about the Honor Code see https://honorcouncil.georgetown.edu/

Communication

General guidelines

Since this is such a large class, we need to introduce some basic communication guidelines.

STUDENT QUESTIONS

  1. General questions: It is much easier to address student questions in a public forum, so that everyone can see the answer. If you have a question about the class, then you are almost certainly not the only one. Therefore, all HW, Lab, classwork, code, bug, etc, questions which are non-personal, should be addressed on a public Google-Spaces channel (or on an alternate software platform if Google-Spaces is not used). That way everyone can see the instructional team’s response. Obviously, DO NOT share large chunks of code or homework solutions in any public channel.
  2. Personal questions, i.e. private correspondence, should be done via email with your professor. DO NOT Direct-message (DM) professors in Google-Spaces, unless the instructional team contacts you first. This is because direct-messages tend to get “lost” much more easily than emails.

COMMUNICATION ORDER: Please follow the following communication hierarchy

  1. Ask a friend: If you question can be answered by a class-mate, in a manner that does not constitute cheating, then that is typically the best place to start.
  2. Public channel: If your question can be addressed in a relevant public Google-Spaces channel, then do so. Also, remember Google-Spaces IS SEARCHABLE!
  3. Email TAs: Some questions about code or the course are not suitable for a public channels. In this case email one of the TAs. TAs reserve the right to tell you to post the question on Google-Spaces if they feel it belongs on the public channel (or forward it to the professors)
  4. Office hours: If there is a persistent bug that you can’t figure out, then please attend office hours with a TA or instructor.
  5. Email one or more professor(s): If you feel your question can ONLY be addressed by your professor, then don’t hesitate to email them, also feel free to CC the other professors on such emails.

EXAMPLES:

  • Questions about why you lost points on a homework, lab assignment, or discussion: Email the TA that graded your assignment
  • Questions about why you lost points on a quiz, lab-presentation, or portfolio assignment: Email the professor that graded your assignment
  • Clarification about a detail associated with a HW assignment: Google-Spaces HW2 channel
  • Can’t figure out why R (or python) won’t read a particular file format: Ask a friend or use the Google-Spaces r or py channel respectively
  • Can’t figure out why a particular bug is occurring in you code: Ask a friend or use Google-Spaces r or py channel respectively
  • Want to ask a TA to help try to trouble-shoot a bug in your code: Email a TA to set up office hours, or attend professor’s office hours

Code of conduct

The following rules of conduct apply to all forms of communication in this class. Both in-person and digital, e.g. Google-Spaces, Canvas, discussion boards, etc.

Our Pledge

We as members, contributors, and leaders pledge to make participation in our community a harassment free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

Our Standards

  • Examples of behavior that contributes to a positive environment for our community include:
  • Demonstrating empathy and kindness toward other people
  • Being respectful of differing opinions, viewpoints, and experiences
  • Giving and gracefully accepting constructive feedback
  • Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
  • Focusing on what is best not just for us as individuals, but for the overall community
  • Examples of unacceptable behavior include:
    • Creating profiles with offensive, unprofessional, or unacceptable user-names or profile pictures. This rule holds for any software platform used in the class, for example, GitHub, Google-Spaces or Canvas.
    • The use of sexualized language or imagery, and sexual attention or advances of any kind Trolling, insulting or derogatory comments, and personal or political attacks
    • Public or private harassment
    • Publishing others’ private information, such as a physical or email address, without their explicit permission
    • Other conduct which could reasonably be considered inappropriate in a professional setting

Expectations

Class material refers to all material produced by the instructional team and common documents provided by Georgetown University that are relevant to this class. These materials are either available in or linked from the class Canvas site. These can include, but not limited to, lecture notes, lecture videos, class documents, assignment and project instructions, and University policy documents, and communication via channels like Canvas.

From students/learners

All relevant class material should be read or consumed before asking a question. Often, the answer is already available in the class materials.

If there are questions regarding particular parts of class material, it should be quoted and linked so that everyone understands the context of the question.

General questions regarding the topics covered in class or are forthcoming, or topics that are relevant but not covered directly, are always welcome

Questions regarding marking of assignments and projects must be accompanied by justification of why you think a higher grade is in order

All queries should be done in a polite, respectful manner, and the instructional team should not feel pressured or badgered.

Critical feedback is important, however, please do it in a kind and respectful way. If you feel there are issues with the course or the instructional style, then please bring them to the attention of the instructional team ASAP. We will do our best to resolve issues and improve your experience.

From the instructional team

All queries will be handled with politeness and respect, and answered in a respectful manner. The student/learner should not be insulted or humiliated or be approached in a bullying or non-collegial manner.

If the answer to a question is already available in the class materials, a link or quote from those materials will be considered a sufficient answer

All answers will be professional, and will reflect both the content of the class and the instructors’ expertise.

Criticism will be constructive.

Scope

This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior consistent with the Georgetown University’s Code of Student Conduct. This includes the entire instructional team, who will collaboratively address issues with any students/learners involved. Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement and may be escalated to University staff as per policies in The Code of Student Conduct.. All complaints will be reviewed and investigated

promptly and fairly. All community leaders are obligated to respect the privacy and security of the reporter of any incident.

Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. Community Impact Guidelines were inspired by Mozilla’s code of conduct enforcement ladder. https://www.contributor-covenant. org For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

Additional Resources

Academic Resource Center

The Academic Resource Center(ARC) is the campus office responsible for reviewing medical documentation and determining reasonable accommodations to students with disabilities.

Laptops

Students MUST have a reliable computer, internet access (with a back-up plan), computer mic, computer speakers, and a computer camera. YOU CANNOT TAKE THIS CLASS if you do not have these items

You can have a laptop running Windows (preferably Windows 10), Linux, or Mac OS X. Any of these will work for the software we will use in this class.

Counseling and Psychiatric Services (CAPS)

As Georgetown faculty, you are among the most important individuals in some of the students’ lives. They may turn to you when they are struggling and in times of need, or you may be one of the first to notice when they are distressed. The CAPS has tips for faculty on how to deal with struggling or distressed students.

Emergency Preparedness and HOYAlert

We encourage all faculty to become familiar with Georgetown’s Office of Emergency Managementand sign up for HOYAlert in order to receive important safety and University operating status updates. Faculty teaching at the Georgetown Downtown campus might also want to sign up for AlertDC to receive safety and traffic updates.

Office of Institutional Compliance and Ethics

The Office of Institutional Compliance and Ethics supports and coordinates many compliance-related activities the University undertakes. This Office, with the endorsement and assistance of the University’s senior leadership, is responsible for leading the development, implementation and operation of the Georgetown Institutional Compliance and Ethics Program.

Office of Institutional Diversity, Equity, and Affirmative Action (IDEAA)

The mission of IDEAA is to promote a deep understanding and appreciation among the diverse members of the University community to result in justice and equality in educational, employment and contracting opportunities, as well as to lead efforts to create an inclusive academic and work environment.

Threat Assessment

Georgetown University established its Threat Assessment program as part of an extensive emergency planning initiative. The program at Georgetown has been developed and implemented to meet current best practices and in accordance with national standards for hazard planning in institutions of higher education and for workplace violence prevention.

Title IX/Sexual Misconduct

Georgetown University and its faculty are committed to supporting survivors and those impacted by sexual misconduct, which includes sexual assault, sexual harassment, relationship violence, and stalking. Georgetown requires faculty members, unless otherwise designated as confidential, to report all disclosures of sexual misconduct to the University Title IX Coordinator or a Deputy Title IX Coordinator. If you disclose an incident of sexual misconduct to a professor in or outside of the classroom (with the exception of disclosures in papers), that faculty member must report the incident to the Title IX Coordinator, or Deputy Title IX Coordinator. The coordinator will, in turn, reach out to the student to provide support, resources, and the option to meet. [Please note that the student is not required to meet with the Title IX coordinator.]. More information about reporting options and resources can be found on the Sexual Misconduct Website

If you would prefer to speak to someone confidentially, Georgetown has a number of fully confidential professional resources that can provide support and assistance. These resources include:

Health Education Services for Sexual Assault Response and Prevention: confidential email sarp@georgetown.edu

Counseling and Psychiatric Services (CAPS): 202.687.6985 or after hours, call (833) 960-3006 to reach Fonemed, a telehealth service; individuals may ask for the on-call CAPS clinician

More information about reporting options and resources can be found on the Sexual Misconduct Website.

https://sexualassault.georgetown.edu/get-help/#Links to an external site.

Jen Schweer, MA, LPC Associate Director of Health Education Services for Sexual Assault Response and Prevention (202) 687-0323 jls242@georgetown.edu (mailto:jls242@georgetown.edu)

Erica Shirley, Trauma Specialist Counseling and Psychiatric Services (CAPS) (202) 687-6985 els54@georgetown.edu (mailto:els54@georgetown.edu)

More information about campus resources and reporting sexual misconduct can be found at http://sexualassault.georgetown.eduLinks to an external site.

Please know that as a faculty member I am committed to supporting survivors of sexual misconduct, including relationship violence and sexual assault. However, university policy also requires me to report any disclosures about sexual misconduct to the Title IX Coordinator, whose role is to coordinate the University’s response to sexual misconduct.

Georgetown has a number of fully confidential professional resources who can provide support and assistance to survivors of sexual assault and other forms of sexual misconduct. These resources include: Getting Help

Special Accommodations

If you believe that you have a disability that will affect your performance in this class, please contact the Academic Resource Center (arc@georgetown.edu) for further information. The center is located in the Leavey Center, Suite 335. The Academic Resource Center is the campus office responsible for reviewing documentation provided by students with disabilities and for determining reasonable accommodations in accordance with the Americans with Disabilities Act (ADA) and University policies.