Major site overhaul: resources hub, content migration, new blog posts, forms
- Redesign /resources as sectioned hub with category pages - Migrate 645 Squarespace CDN images to local /images/content/ - Create 9 new news/blog posts with event photos - Fix blog post slugs (rename gibberish filenames) - Rename Design Blog to Design Blogs across site - Remove education page, replace with Platform in nav - Redesign rover repair request form with dynamic rover entries - Add school search combobox to contact, store, and repair forms - Extract shared KNOWN_SCHOOLS data - Make /rover-expansion-3d-printing dynamically pull from MDX - Add related resources sections to product pages - Fix homepage broken /quote links to /store - Store page: sample kit cards, inline quote builder, mailing list opt-in
This commit is contained in:
Tim Hadwen
@@ -11,9 +11,7 @@ Micromelon Code Editor 2.8.3 was released in April of 2025. This post will detai
|
||||
|
||||
## Change: Institution Account System
|
||||
|
||||
#### **The Problem**
|
||||
|
||||
Previously in the Code Editor accounts were split between home users and institution users like admins, teachers, instructors and students. Until now, there has been no easy way to transition between all of these account types. For example, once a student account is created, if you wish to remove that account from your school you would have to delete the student account and all of it’s work. This was an issue if your institution has purchased a set number of licences and changes over student accounts per term. Each time you cycle your student accounts, you would need to be delete and re-create all your students. From **Code** **Editor 2.8.3** this is no longer the case.
|
||||
#### **The Problem** Previously in the Code Editor accounts were split between home users and institution users like admins, teachers, instructors and students. Until now, there has been no easy way to transition between all of these account types. For example, once a student account is created, if you wish to remove that account from your school you would have to delete the student account and all of it’s work. This was an issue if your institution has purchased a set number of licences and changes over student accounts per term. Each time you cycle your student accounts, you would need to be delete and re-create all your students. From ** Code** ** Editor 2.8.3** this is no longer the case.
|
||||
|
||||
#### **The Solution**
|
||||
|
||||
@@ -25,11 +23,11 @@ The teacher dashboard will largely stay the same. The difference now is that ins
|
||||
|
||||
**Old: Creating Students**
|
||||
|
||||
|
||||
|
||||
|
||||
**New: Inviting Students**
|
||||
|
||||
|
||||
|
||||
|
||||
## **New: Quick Join Code**
|
||||
|
||||
@@ -37,7 +35,7 @@ Besides the old tools being updated to the invite system. There is now a new too
|
||||
|
||||
#### What is a Quick Join Code?
|
||||
|
||||
|
||||
|
||||
|
||||
Every class has a unique 9 digit Quick Join Code.
|
||||
|
||||
@@ -45,7 +43,7 @@ You can share this with your students and they can use it to join your class & s
|
||||
|
||||
You can find the Quick Join Code for a class next to the class selection dropdown.
|
||||
|
||||
|
||||
|
||||
|
||||
#### How Students Use Quick Join Codes
|
||||
|
||||
@@ -57,9 +55,9 @@ You can find the Quick Join Code for a class next to the class selection dropdow
|
||||
|
||||
## New: Sign In Through Google, Microsoft and Apple
|
||||
|
||||
Previously Micromelon Accounts were created with a username, password and email. We’ve now added the ability to sign in through your **Google**, **Microsoft**, and **Apple** accounts.
|
||||
Previously Micromelon Accounts were created with a username, password and email. We’ve now added the ability to sign in through your **Google**,** Microsoft**, and** Apple** accounts.
|
||||
|
||||
|
||||
|
||||
|
||||
#### **Using The Sign-In Services**
|
||||
|
||||
@@ -75,7 +73,7 @@ After you’ve authorised Micromelon to use your service details, you’ll be re
|
||||
|
||||
We’ve built a new tool for recording sensor data from the rover during program execution. After running a program, users can open up the new **Data Recorder** tool and download a spreadsheet which contains all values captured by the onboard rover sensors. Let’s look at how to use the data recorder.
|
||||
|
||||
|
||||
|
||||
|
||||
#### Using The Data Recorder In The Code Editor
|
||||
|
||||
@@ -87,7 +85,7 @@ We’ve built a new tool for recording sensor data from the rover during program
|
||||
|
||||
- Press **Save To CSV** to save your `.csv` .file to your computer
|
||||
|
||||
|
||||
|
||||
|
||||
#### Using The Data After Saving
|
||||
|
||||
@@ -95,13 +93,13 @@ After saving your `.csv` file, you can open it in excel or excel like programs t
|
||||
|
||||
#### Understanding The Data
|
||||
|
||||
While your rover is executing your code, it snapshots the data from it’s onboard sensors roughly every 50-100 milliseconds. Each time this snapshot happens, the data recorder will save the snapshot. Once you export your data, each snapshot recorded will become a new row. The first row of data is a snapshot from the start of your code executing. The last row is a snapshot of the end of your code executing. When saving your data, you have the choice of picking which sensors to include. Regardless of which sensors you pick, the first two columns will always be `**time** and **time_milliseconds**.` These two columns are different representations of the point in time this snapshot was created.
|
||||
While your rover is executing your code, it snapshots the data from it’s onboard sensors roughly every 50-100 milliseconds. Each time this snapshot happens, the data recorder will save the snapshot. Once you export your data, each snapshot recorded will become a new row. The first row of data is a snapshot from the start of your code executing. The last row is a snapshot of the end of your code executing. When saving your data, you have the choice of picking which sensors to include. Regardless of which sensors you pick, the first two columns will always be `**time** and ** time_milliseconds**.` These two columns are different representations of the point in time this snapshot was created.
|
||||
|
||||
- `**time**` is a UTC timestamp. [Learn more about UTC timestamps here.](https://en.wikipedia.org/wiki/Coordinated_Universal_Time)
|
||||
|
||||
- `**time_milliseconds**` is a unix timestamp in milliseconds. [Learn more about unix timestamps here.](https://en.wikipedia.org/wiki/Unix_time)
|
||||
|
||||
The rest of the columns of your sheet will be for each sensor you chose to include in your `.csv` file. So if you chose to save the **Ultrasonic** sensor, you can find it’s data in the column with the header **Ultrasonic**.
|
||||
The rest of the columns of your sheet will be for each sensor you chose to include in your `.csv` file. So if you chose to save the **Ultrasonic** sensor, you can find it’s data in the column with the header ** Ultrasonic**.
|
||||
|
||||
## Change: Interface Refresh
|
||||
|
||||
@@ -113,6 +111,4 @@ We’re always aiming to improve the Code Editor. In this release we have update
|
||||
|
||||
To get the latest version,
|
||||
|
||||
- Microsoft Users: Open the Code Editor. In the top bar click **File** -> **Check for Updates**
|
||||
|
||||
- Mac Users: Open the Code Editor. In the app menu click **Micromelon IDE** -> **Check for Updates**.
|
||||
- Microsoft Users: Open the Code Editor. In the top bar click **File **->** Check for Updates **- Mac Users: Open the Code Editor. In the app menu click** Micromelon IDE **->** Check for Updates**.
|
||||
|
||||
Reference in New Issue
Block a user