START HERE - Step-by-Step for Every Task This Week

Follow these steps for your tasks this week. You should not need to ask anyone how to start. Each task on the Tasks board has the same name as its step here.

• RAYLEN - 1. Plot-label email: open the "Confirm tower 1, 4 & 5" task, copy the draft text, paste into a new email, add Dr. Kuloyo's address, send. Then move that task to Complete.
• RAYLEN - 2. Scheduling email: same steps, using the draft on the "Schedule data-walkthrough call" task.
• RAYLEN - 3. Shared GitHub repo: follow the GitHub steps below, then invite Rory and Alex.
• RAYLEN - 4. Walkthrough: reply to Shell with the day and time, then edit the "Flux tower farm walkthrough" task with the real date.
• RAYLEN - 5. Wednesday update: pull the key points from the "Data Handoff Call" and "MVP Dashboard Build Guide" entries, add a screenshot of the first chart when it exists, and list the open questions for Shell.
• RAYLEN - 6. Plot labels: when Shell replies with what towers 001, 004 and 005 are, send the answers to Rory so the labels get updated in the data.
• RORY - 1. Accept the GitHub invite (email or github.com notifications), then clone the repo: open the repo page, click the green Code button, copy the HTTPS link, and run "git clone <paste link>" in a terminal.
• RORY - 2. Before writing code, read the Flux Tower Data Dictionary in this Research Hub. Pay attention to the sign convention and the QC flag notes.
• RORY - 3. Create one readings table with a tower_id column, a granularity column (daily or 30min), and one column per CSV field. Keep each QC flag next to its value.
• RORY - 4. Write the import script: read the 8 daily CSVs, turn "NA" into empty values, and insert rows in batches.
• RORY - 5. Test on one tower first. Check the row count matches the CSV, then run all 8 towers.
• RORY - 6. Post in the team chat when the daily data is loaded so Alex can start the Current Conditions card.
• RORY - 7. Then add the 30-minute files the same way (about 15MB each).
• ALEX - 1. Accept the GitHub invite and clone the repo (same as Rory, step 1).
• ALEX - 2. Set up the project: in the repo folder run "npx create-next-app@latest", choose TypeScript and Tailwind, keep the other defaults, then commit and push.
• ALEX - 3. Wireframes: sketch two pages, Current Conditions (one card per tower) and Historical Trends (tower dropdown, date range, one chart per variable). Draw a phone version and a desktop version of each. Share photos in the team chat.
• ALEX - 4. When Rory says the data is loaded, build one tower card with real numbers, then reuse it for the other 7 towers.
• ALEX - 5. Check every page at phone width before you call it done.
• EVERYONE - GITHUB SETUP (Raylen does this once): go to github.com, sign in, click the + at the top right, choose New repository. Name it fluxview-shell, pick Private, tick Add a README, click Create repository.
• EVERYONE - INVITE: on the repo, click Settings, then Collaborators (or Manage access), click Add people, and type each teammate's GitHub username. They get an email to accept.
• EVERYONE - DAILY ROUTINE: before you start work, run "git pull". When you finish, run "git add .", then "git commit -m "short description of what you changed"", then "git push".
• EVERYONE - PASSWORD PROMPT: GitHub does not accept your account password in the terminal. Create a Personal Access Token at Settings, then Developer settings, then Personal access tokens, and paste that when asked.
• EVERYONE - DATA FILES: do not commit the CSV files to GitHub. They are large, and Shell already sent them to everyone by email. Use your email copy locally.
• IF YOU ARE STUCK: post in the team chat with a screenshot and the exact error message. Try at most twice on your own first.