N-Slit-Visualization
The goal of this project is to provide an interactive visualization of the intensity curve resulting from the quantum mechanical effects of N-Slit interference and diffraction.
This project was completed during Fall 2018 as part of a James Scholar Honors project for the University of Illinois Department of Physics.
Using React with p5.js
This project demonstrates the possibility of combining React and p5.js.
React is one of the most popular JavaScript libraries for creating single page applications.
p5.js is a JavaScript library with a full set of drawing functionality.
Check the online version here.
The basic idea is that the p5.js sketch is wrapped in a React component. The data that comes into the sketch is passed on to this component as props. Callbacks are used to return information back from the sketch to the application.
A much more advanced example, built on the same concept, can be found here. A special thanks to Atorov of whose code the React backend and P5 wrapper are based off.
Project Structure
The project is build on Create React App.
For the project to build, these files must exist with exact filenames:
public/index.htmlis the page template;src/index.jsis the JavaScript entry point.
You can delete or rename the other files. You may create subdirectories inside src. For faster rebuilds, only files inside src are processed by Webpack. You need to put any JS and CSS files inside src, otherwise Webpack won’t see them.
Only files inside public can be used from public/index.html.
You can, however, create more top-level directories. They will not be included in the production build so you can use them for things like documentation.
Available Scripts
In the project directory, you can run:
npm start
Runs the app in the development mode. Open http://localhost:3000 to view it in the browser. The page will reload if you make edits. You will also see any lint errors in the console.
npm test
Launches the test runner in the interactive watch mode.
npm run build
Builds the app for production to the build folder. It correctly bundles React in production mode and optimizes the build for the best performance. The build is minified and the filenames include the hashes. Your app is ready to be deployed.
npm run eject
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.