🎯 Summer 2024 Planning meetings

[JamesPHoughton]

We'll try a slightly different format for our meeting notes this summer, and keep them all in a single thread. This is it!

[JamesPHoughton]

Monday June 2, 2024

Morning (Full group)

• Office space, desks, keys, etc.
• Setting up computers
  • [ ]
• Using github
  • How to write a good issue
  • How to use issues to track work process
  • Github branching, pull requests, etc.

Afternoon

• [ ]

[JamesPHoughton]

Week 2 Planning, monday June 10

common sense project

• updates on the existing tasks:
  • internationalization support @dankim444
    • used the useTranslation hook to translate the important parts of the website.
    • Working on tests using cypress
    • Getting translations from google translate and chatGPT
    • Make sure to take the language flag from the user that respects what language the browser asks for
  • replacing hardcoded variables @acao22
    • found most things, still working to find the remaining
    • import is ok, don't need to have dynamic loading of values
    • Look at using surveyjs and surveys library
    • look at issue 148 and 128 as next issues.
  • meeting times:
  • 1-2 Mondays for a larger commonsense meeting.

deliberation

Structuring the week

• Items from last week that remain open
  • typescript: nearly everything is there, no errors running the build command.
  • next steps: get cypress running with the built version and then merge to main.
• Introducing new tasks
  • merge kimberly's code (Implement ability to render actual elements researcher-portal#30) @JamesPHoughton
  • have code running on server by Friday (Deploy to server researcher-portal#32)
  • have everything else in PR by Friday afternoon
  • update to nextJS 14 Update to NextJS 14 researcher-portal#42
  • research higher level react form libraries and using zod to validate form inputs
• Plan for timings this week
  • James anniversary wednesday
  • Friday wrapup meeting 11-11:30 (James and Eric's kids have a half day)

[JamesPHoughton]

Week 2 wrapup, Friday June 14

• what did you work on with each other this week?
  • @evanping worked with james and christa to get the project to build properly, updated errors and got it to work. Read into React-hook-forms with christa.
  • @christabusho same as Evan, plus going more deeply into react-hooks-form
  • @acao22 worked fairly separately, made the daily standup into a slack channel. Worked on hard-coded variables in JSON.
• what was the hardest thing you had to do this week?
  • @acao22 the codebase is still fairly new, so still learning way around the code. Interface type errors also difficult.
  • @christabusho debugging type errors. Was difficult to think about how to research the separate libraries as a team, because of the coordination problem.
  • @markwhiting getting a paper written
  • @evanping debugging typescript and getting project to build.
  • @JamesPHoughton typescript
• what is still open?
  • update popup to use react-hook-forms researcher-portal#48
  • still needing to get hardcoded variables closed
  • need to look at surveyjs Explore whether to replace surveyJS with a custom renderer surveys#183
  • Merge kimberly's code
• what did we finish?
  • @evanping - built the project, tested with cypress, tests are automated, got the website to deploy, settled on a form library.
  • @acao22 - remove hardcoded variables in a number of files, on the branch and listed in the issue
  • @christabusho - same as even, making the decision was good
  • @markwhiting - ran an experiment for commonsense, almost done with the task mapping paper
  • @JamesPHoughton - set up bug report and feature templates

todo:

• share typescript learning resources.

[JamesPHoughton]

Week 3 planning meeting, Monday June 17

Getting started

• What is the best class you've taken so far, and why?

Open issues

Deliberation

• Implement ability to render actual elements researcher-portal#30 @JamesPHoughton
• update popup to use react-hook-forms researcher-portal#48
• Figure out how to reuse zod types for form inputs researcher-portal#44

Common sense

• Language support for experiment website commonsense-platform#145
• Remove hard coded variable names from processing code commonsense-platform#111

New issues

Shared

• Explore whether to replace surveyJS with a custom renderer surveys#183

Common sense

• Language support for statements commonsense-platform#146
• The answers page on dashboard should 1) show statement commonsensicality, 2) let me change my mind commonsense-platform#128

Deliberation

• [FEATURE]: Default/Sample YAML Treatment researcher-portal#54
• Add warning when code didn't save because of bad yaml researcher-portal#15

Logistics

• Wednesday is an institute holiday

Business arising:

• check on whether we can use code coverage with cypress

[JamesPHoughton]

Week 3 wrapup, friday June 21

How did you help each other this week?

• @christabusho: spent some time dividing up the work and how you're approaching the work
• @dankim444: mostly working on separate issues, but planning some pair-programming on wednesday
• @evanping: checking in on each other and clarifying code
• @acao22: Mostly separate stuff
• @JamesPHoughton: zod schema development with christa
• @markwhiting: worked with amir, doing a walkthrough of the infrastructure for everyone. Conversing in issues on lots of the stuff angie is working on.

What did you learn this week?

• @christabusho: more about zod, using tests with zod in existing code from kimberly
• @acao22: Mostly front end and API stuff - the math behind commonsense
• @markwhiting: how to make more efficient wrappers for mturk, lots of edge cases
• @dankim444: more comfortable with backend
• @evanping: react hook forms
• @JamesPHoughton: qualtrics js scripting, learning about zod

What did we finish?

Common sense

• issue 146, set up the translation table
• 128-change-answers
• new notification system for turkers in the panel, got a lot more participants (a few thousand)

Deliberation

• Merging code: Render delib empirica researcher-portal#36
• Added a bunch more zod schemas to be able to use them with react-hooks form
• mostly converted the addpopup to use react hook form, requires some updating with new schemas
• Implement ability to render actual elements researcher-portal#30

What is still open?

Watts-Lab/surveys#183

Common sense

• still filling in a translation table
• figuring out how to display "commonsensicality" to end user
• looking at cypress testing for code coverage
• fixing the percentages that others agree

Deliberation

• Figure out how to reuse zod types for form inputs researcher-portal#44
• update popup to use react-hook-forms researcher-portal#48
• [FEATURE]: Default/Sample YAML Treatment researcher-portal#54
• still look at using react-hook-form to replace surveyJS

[JamesPHoughton]

Week 4 Kickoff, June 24, 2024

Getting started

• What adventures did you have this weekend?

Open issues

• Explore whether to replace surveyJS with a custom renderer surveys#183
• looking at cypress testing for code coverage

Deliberation

• Figure out how to reuse zod types for form inputs researcher-portal#44
• update popup to use react-hook-forms researcher-portal#48
• [FEATURE]: Default/Sample YAML Treatment researcher-portal#54

Common sense

• Remove hard coded variable names from processing code commonsense-platform#111
• Language support for statements commonsense-platform#146
• The answers page on dashboard should 1) show statement commonsensicality, 2) let me change my mind commonsense-platform#128

New Issues

Deliberation

• [FEATURE]: Render remaining components from deliberation-empirica researcher-portal#64
• Add warning when code didn't save because of bad yaml researcher-portal#15

Common sense

• Treatment of statements is inconsistent commonsense-platform#150
• At SEAS and CETs request: public access DB should be behind an API or something else to secure access commonsense-platform#147

[JamesPHoughton]

Week 4 Wrapup: June 28, 2:00pm

How did someone help you this week?

• @evanping - christa helped implementing react hook form, understanding zod and typing
• @markwhiting - amir helped set up a demo for a talk about the atlas project
• @dankim444 - mark helped with setting up amazon translate API, amir helped with backend stuff, surveys repo
• @christabusho - Evan helped understand how the popup worked, james helped understand how the zod schema would be used.
• @shapeseas - mark helped with website analytics
  @JamesPHoughton - mark helped me get a qualtrics survey fixed

What isn't working for you at the moment?

• @dankim444 - got sick this week. Duplicate statements in a test - translations arent working as expected
• @markwhiting - having code in 3 different languages, need to scale up python for machine learning
• @evanping - did a lot of reworking of the popup modals, and now cypress tests are broken. James broke a lot of the IDs for components.
• @JamesPHoughton - node version management
• @christabusho - understanding some fields of the element object when using zod schemas, some config issues with prettier
• @shapeseas - supposed to be stretching in post-surgery recovery. Needs reminders.

What did we finish?

Deliberation

• 🤷‍♂️ Templating syntax for treatment definitions #448
• Mostly Figure out how to reuse zod types for form inputs researcher-portal#44
• Mostly: update popup to use react-hook-forms researcher-portal#48
• Bug with old form fields persisting when they shouldn't
• Dropdown for survey names

Common sense

• Mostly: Language support for statements commonsense-platform#146
• Lots of learning about mySQL.
• Almost ready to start running bigger experiment.

What is still open?

Common sense

• 111 removing hardcoded variable names commonsense-platform#152
• opening new issues (code coverage, other language supports from discussion with mark on Tuesday)
• angie has a few things open, and some stuff to work on.

Deliberation

• implement the stage component from deliberation-empirica (instead of building up the page element at a time) researcher-portal#66
• not really done updating the add popup with the new zod schema validations.
• issues we opened monday
• implement the stage component from deliberation-empirica (instead of building up the page element at a time) researcher-portal#66
• fix remaining issues with conversion
• merging various branches
• [FEATURE]: Default/Sample YAML Treatment researcher-portal#54

For Monday:

• plan some time for merging branches

[JamesPHoughton]

Week 5 Planning meeting, July 1

Getting Started

• What personal projects/hobbies are you working on this summer?
• @acao22 - I've been dancing more often, and also playing a lot of Pokémon Go & Smash Bros :) when I have time I want to pick up on more figure skating practice as well
• Josh has been running more, getting back to Karate practice
• @dankim444 - getting into an exercise routine, get some weightlifting PRs
• @christabusho - more gym workouts, US driving license
• @shapeseas - working on his zoom filters.... Working with a minicomputer, making a steampunk project, work on the car
• @evanping - exercise, swimming, (but the pool is closing!)
• @JamesPHoughton - iNat, also parenting.

Open Issues

Deliberation

• implement the stage component from deliberation-empirica (instead of building up the page element at a time) researcher-portal#66
• [FEATURE]: Default/Sample YAML Treatment researcher-portal#54
• update popup to use react-hook-forms researcher-portal#48
• Figure out how to reuse zod types for form inputs researcher-portal#44

Mostly what needs to be done next is merge some code

Common Sense

• 128 change answers commonsense-platform#157
• note: @acao22 - not sure where to put this but I created a PR and all cypress tests pass, should be compete
• 111 removing hardcoded variable names commonsense-platform#152
• note: @acao22 - fixed failing cypress bug, should be good to merge and close

Mostly what needs to be done next is merge some code
@markwhiting @dankim444 will have a conversation about how to manage duplicate statements

• issue with a number of the statements being so similar that they translate to identical statements in the other language. Approaches to solving: either remove statements that are similar, or maybe have a human translator who can address the nuances and subtle differences between statements do the translation to preserve that nuance.

New Issues

Common Sense

Deliberation

• [Bug]: Render panel overflows researcher-portal#63

notes

We will play by ear to see if we want to have our Friday meeting or to take off Friday, based on progress during the week.

[markwhiting]

Just adding here because editing was not working (perhaps @JamesPHoughton is editing at the same time):

Common Sense

• Treatment of statements is inconsistent commonsense-platform#150
• almost done 128 change answers commonsense-platform#157
• almost done 111 removing hardcoded variable names commonsense-platform#152
• almost done Language support for statements commonsense-platform#146

New Issues

Common Sense

• Evaluate user flow through the platform, plan issues and tests commonsense-platform#158

[JamesPHoughton]

Week 6 Planning meeting July 8

Getting started

• Of all the things you've ever done to celebrate July 4, what was the best?

Open issues

Common sense

• Treatment of statements is inconsistent commonsense-platform#150
• 128 change answers commonsense-platform#157
• Language support for statements commonsense-platform#146
• Evaluate user flow through the platform, plan issues and tests commonsense-platform#158

Deliberation

• implement the stage component from deliberation-empirica (instead of building up the page element at a time) researcher-portal#66
• [FEATURE]: Default/Sample YAML Treatment researcher-portal#54
• update popup to use react-hook-forms researcher-portal#48
• Figure out how to reuse zod types for form inputs researcher-portal#44
• [Bug]: Render panel overflows researcher-portal#63
• Decide the structure of the storage of markdown files deliberation-portal#15

New issues

Deliberation

• decide how to represent the information that "stage" needs in order to determine what to render and what to hide researcher-portal#65
• [FEATURE]: Use CSS from deliberation-empirica in render window researcher-portal#56

Common sense

[JamesPHoughton]

Week 6 review meeting

Getting started: What tool did you learn about or learn how to use better this week?

• @JamesPHoughton bayesian models with logit link functions
• @acao22 AWS lambdas and rds
• @dankim444 Practice with python and Pandas, openAI's embedding tool. Scikit learn cosine similarity
• @christabusho more familiar with styling CSS
• @evanping lots more familiar with zod type schemas, making sure validation works with cypress tests, learned about deliberation-empirica

What did we finish

deliberation

• Mostly done: implement the stage component from deliberation-empirica (instead of building up the page element at a time) researcher-portal#66
• Mostly done, need to merge with evan's code: update popup to use react-hook-forms researcher-portal#48
• Reworked cypress tests so that everything successfully runs. Tweaked the validation
• Mostly done: [Bug]: Render panel overflows researcher-portal#63

Common sense

• cleaning statements repo, waiting for mark's approval
• need to run cypress more frequently
• lots of styling and UI pieces

What is open and wants support

common sense

• feeling good about where we are

deliberation

• feeling pretty good, working on getting the stage renderer together.
• thinking about the next steps and what to prioritize
• started looking into the vs code extension, how we move the existing app there. First, hello world!

Waiting on / todo monday

• creating a new stage should allow an empty array
• responsive scaling for render panel
• merging christa and evan's changes to each other, then merge to main

[JamesPHoughton]

Week 7 (!!) planning meeting

Getting started: Strategizing the home stretch

What is your priority, what should we punt, what's our strategy going to be.

• @dankim444: Priority - get PRs in and merged, fix small bugs in existing PRs. Want to add Atlas stuff. Strategy: Get back into the daily standup to help unstick issues and support one another.
• @acao22: Priority - finish AWS stuff, merge minor stuff from sign in page. Priority: Been doing a variety of issues, want to work on larger point-toable piece. Strategy: Keep using issues to coordinate
• @christabusho: Priority: adding remaining components to displays. Start collaborating on poster presentation. Strategy: short meeting later in the week about the presentation.
• @evanping: Priority: adding more visual changes you can see, to be able to show off. push off smaller bugs to the term. Strategy.
• @markwhiting: Priority - how to convince students to continue working in the fall. Done nice work around finishing issues on common sense. Good to launch experiment by end of summer. Stretch goal: get Atlas stuff done for summer. Strategy: Have more conversations about atlas.
• @JamesPHoughton: priority: render an existing actual experiment, side panel for extra info, plus accessing different files. Strategy: share actual treatment we want to use for an experiment.

Issues on the cusp of closing

Deliberation

• update popup to use react-hook-forms researcher-portal#48
• Figure out how to reuse zod types for form inputs researcher-portal#44
• implement the stage component from deliberation-empirica (instead of building up the page element at a time) researcher-portal#66
• [Bug]: Render panel overflows researcher-portal#63

Common sense

• Fix minor CSS/UI issues in the main experiment website commonsense-platform#159
• Add translations for statements in 10 languages commonsense-statements#15

Issues that need work this week:

Common sense

• At SEAS and CETs request: public access DB should be behind an API or something else to secure access commonsense-platform#147
• Language support for statements commonsense-platform#146
• Add signout button and improve user signin/signout flow commonsense-platform#160
• Treatment of statements is inconsistent commonsense-platform#150

Deliberation

• decide how to represent the information that "stage" needs in order to determine what to render and what to hide researcher-portal#65
• [FEATURE]: Use CSS from deliberation-empirica in render window researcher-portal#56

New Issues

[JamesPHoughton]

Week 8 Planning meeting

Getting Started: What are you hoping to learn in the next 6 months?

• @acao22: complete backend stuff, mostly know front end, and want to become a more solid full-stack developer. provisioning, databases, etc.
• @christabusho: UI/UX design - have some instruction, want practice. Dating a data science class, want to learn more about that.
• @dankim444: learn more general software dev practices in the industry. CI/CD and devops. Machine learning (taking CIS 520 w/ Jacob Gardner)
• @joshnguyen99: human studies, more experiments
• @markwhiting: shorter publication loop. Maybe using LLMs?
• @JamesPHoughton: what mark said. Neural network regressions, also how to compare predictive power of NNs with bayesian glm/hierarchical models.

Closed last week:

Common sense

• 159 styling bugs angie commonsense-platform#164
• Change /getanswers to filter based on createTime and also fix multiple toggle bug commonsense-platform#165
• 165 Filter statements by createAt() and also fix toggling multiple answers not updating properly commonsense-platform#166
• 160 sign in fixes: navigate to Dashboard when clicking magic link and added sign out button commonsense-platform#167
• Add translations for statements in 10 languages commonsense-statements#15

Stuck/Blocked issues:

Deliberation

• implement the stage component from deliberation-empirica (instead of building up the page element at a time) researcher-portal#66

Common Sense

Other Open issues:

Common Sense

• At SEAS and CETs request: public access DB should be behind an API or something else to secure access commonsense-platform#147
• Workflow for automated translations and removal of duplicate statements using Github Actions commonsense-statements#18
• Treatment of statements is inconsistent commonsense-platform#150
• Language support for statements commonsense-platform#146

Deliberation

• [Bug]: Render panel overflows researcher-portal#63
• [FEATURE]: Use CSS from deliberation-empirica in render window researcher-portal#56
• decide how to represent the information that "stage" needs in order to determine what to render and what to hide researcher-portal#65

[JamesPHoughton]

Getting started:

What was the most difficult thing you did this week

• @shapeseas: Got poison ivy, had to deal with the consequences! What to do now with the rest of the yard?
• @dankim444: Time management, helping some high school data science projects and also doing a bunch of other stuff
• @acao22: Moving stuff to new apartment
• @markwhiting: Carried a really heavy bag of groceries and a baby. Got a bruise.
• @christabusho: Time management too! Semester abroad starts this fall, there was a pre-orientation meeting, visa interview.
• @JamesPHoughton: getting rid of wasps
• @evanping: preparing for recruiting season.

What did we finish

• Workflow for automated translations and removal of duplicate statements using Github Actions commonsense-statements#18
• 160 sign in fixes: navigate to Dashboard when clicking magic link and added sign out button commonsense-platform#167
• Workflows for automated translations, removal of duplicates, and calculating translation costs commonsense-statements#19
• [Bug]: Build error: Document component is being run on the server side instead of the client side  researcher-portal#69
• implement the stage component from deliberation-empirica (instead of building up the page element at a time) researcher-portal#66
• update popup to use react-hook-forms researcher-portal#48
• Figure out how to reuse zod types for form inputs researcher-portal#44

What is almost done

• Language support for statements commonsense-platform#146

What is still open

• [Bug]: Render panel overflows researcher-portal#63
• [FEATURE]: Use CSS from deliberation-empirica in render window researcher-portal#56

What is stuck

• At SEAS and CETs request: public access DB should be behind an API or something else to secure access commonsense-platform#147

Reminder student mini-conference

• All virtual this year, 10-2ish, Friday August 2nd
• Presentation from last year: https://docs.google.com/presentation/d/1fJ2psMq13eEppLjs9nJhk0eg-zq0E-eU/edit#slide=id.g25de851fc18_1_2

[JamesPHoughton]

Monday July 29

open issues

Deliberation

• [Bug]: Render panel overflows researcher-portal#63
• [FEATURE]: Use CSS from deliberation-empirica in render window researcher-portal#56

Common Sense

• At SEAS and CETs request: public access DB should be behind an API or something else to secure access commonsense-platform#147
• Language support for statements commonsense-platform#146

new issues

• PURM presentation researcher-portal#73

Deliberation

• Do a full review of layout/CSS styling to make positioning consistent. #869
• [FEATURE]: Mock useGlobals to let us get the path to prompt files researcher-portal#72

[JamesPHoughton]

August 5 Planning meeting

Getting started: What have you learned this summer?

• React hook forms
• Git Ettiquite? PRs, issues
• CSS (!&^#*@^&) (formatting websites)
• CSS!!!!! (computational social science)
• API endpoints + SQL querries
• React "Contexts"
• Navigating a large code base
• Monkey patching node so that it works
• Enabling multi-language support for websites
• ZOD validations and schemas
• Typescript
• Cypress testing
• Mock objects for testing
• Dealing with unmodifiable submodules/dependencies
• Python and data cleaning practices
• Github copilot
• Debugging techniques
• Organizing Agile(ish) workflow with multiple projects
• Github Actions
• Communicating tasks and work in a research environment
• LIVE DEMO in a conference
• Choose libraries and design architectures

All open tasks, what will we do with them?

Deliberation

• [Bug]: Render panel overflows researcher-portal#63 ✅
• Do a full review of layout/CSS styling to make positioning consistent. #869 ✅
• [FEATURE]: Use CSS from deliberation-empirica in render window researcher-portal#56 (comment) ➡️

Common Sense

• Treatment of statements is inconsistent commonsense-platform#150 ✅
• Language support for statements commonsense-platform#146 ✅
• At SEAS and CETs request: public access DB should be behind an API or something else to secure access commonsense-platform#147 ➡️ ✅
• @dankim444 Write up really detailed and amazing wowsa documentation for the translation pipeline - maybe extract a demo that is it's own public repo.

High level goals for the fall

Deliberation

• Want to be able to edit markdown stuff easily
• Want multiple users to be able to use
• Want to be able to customize stage configurations (new panel)
• Drag and drop
• Good feedback for the user when they make a mistake
• Work out how to push treatment files, etc. into the actual experiment pipeline
• Intro sequences and multiple treatment descripttions
• Templating in the editor
• Have a plan for larger infrastructure design, considering the intended audience, how much effort we want to put into maintaining infrastructure. Talk with users and see if choices we are making make it harder for them to use the platform. Does pushing people to use github more explicitly hurt or help, by getting more people involved at the design level
• Empirica Dependency. How vulnerable are we to it's maintenance schedule?
• Long term model - Qualtrics for video discussions? Specifying experiments as manifest - how can we get more value out of that? 🌪️Spinoff? 🐇Rabbit hole?

Common Sense

• Improving user sign-in sign-out flow
• UI/UX design improvements generally
• Adding flexibility for surveys
• Do people who work together all form a set of common sense ideas? Commonsensicality of a team, organization?
• What is a causal mechanism for formation of common sense in a group? Homophily vs influence. Is this different than for other types of beliefs.
• Remediation? correcting metaperceptions? Correlations between expectations and types of prejudice?

Personal / Skill development

• More practice with full stack dev for @dankim444, maybe dive into atlas, exposure to other projects.
• Keep the energy that we managed during the summer when we get into term.
• @evanping back-end development experience, log-in systems, etc.
• learn how to manage filesystem stuff
• @acao22 @dankim444 unit testing, debugging, etc.
• @christabusho time management, keeping on top of issues, balancing effort

Tactical