|
Smartlock
|
Data Structures | |
| struct | spi_aml_master_config_t |
| AML SPI master parameters available for superior drivers (pointers). More... | |
| struct | spi_aml_slave_config_t |
| AML SPI slave parameters available for superior drivers (pointers). More... | |
| struct | spi_aml_transfer_t |
| SPI transfer structure. More... | |
| struct | tmr_aml_pwm_ch_t |
| AML timer channel parameters for PWM mode. More... | |
| struct | tmr_aml_outcmp_ch_t |
| AML timer channel parameters for output compare. More... | |
| struct | tmr_aml_config_t |
| AML timer parameters available for superior drivers (pointers). More... | |
| struct | tmr_sdk_pwm_t |
| PWM mode configuration for TPM device for KSDK. More... | |
| struct | tmr_sdk_outcmp_ch_t |
| Configuration of a channel for output compare mode. It contains input parameters of SetupOutputCompare function of TPM device for KSDK. More... | |
| struct | tmr_sdk_outcmp_t |
| Output compare mode configuration of TPM channels for KSDK. More... | |
| struct | tmr_sdk_incpt_ch_t |
| Configuration of a channel for input capture mode. It contains input parameters of SetupInputCapture function of TPM device for KSDK. More... | |
| struct | tmr_sdk_incpt_t |
| Input capture mode configuration of TPM channels for KSDK. More... | |
| struct | tmr_sdk_config_t |
| Initial configuration of the TPM device for KSDK. More... | |
| struct | tmr_data_t |
| Device data structure needed by AML driver in KSDK. More... | |
Timer configuration (SDK specific) | |
General timer configuration and PWM mode configuration are needed by AML driver. Types are defined according to used SDK (KSDK or S32 SDK) and peripheral type (TPM or FTM). | |
| typedef tpm_config_t | tmr_config_t |
| SDK specific timer general configuration. | |
| typedef tpm_chnl_pwm_signal_param_t | tmr_sdk_pwm_ch_config_t |
| SDK specific PWM mode configuration of a channel. | |
| tmr_sdk_outcmp_ch_t* chConfig |
Array of PWM channels parameters.
| tmr_sdk_incpt_ch_t* chConfig |
Array of PWM channels parameters.
| tpm_chnl_t chnlNumber |
The channel number.
| tpm_chnl_t chnlNumber |
The channel number.
| tpm_chnl_pwm_signal_param_t* chnlParam |
Configuration of PWM channel's.
| tpm_clock_source_t clkSrc |
Timer clock source selection.
| tpm_clock_source_t clkSrc |
Clock source selection.
| uint32_t compareValue |
Value to be programmed in the CnV register.
| tpm_pwm_mode_t mode |
The counter operation mode.
The output action.
Selection of capture edge.
| uint8_t numOfChnls |
Number of channels to configure.
| uint8_t numOfChnls |
Number of channels to configure.
| uint8_t numOfChnls |
Number of channels to configure.
| uint32_t pwmFreq_Hz |
The counter frequency in Hz.
| uint32_t srcClck_Hz |
The counter clock in Hz.
| tmr_sdk_outcmp_t tmrCmpConf |
TPM configuration of channels for output compare mode.
| tpm_config_t tmrConf |
TPM configuration passed into TPM_Init function.
| tmr_sdk_incpt_t tmrCptConf |
TPM configuration of channels for input capture mode.
| tmr_sdk_pwm_t tmrPwmConf |
TPM configuration including frequency and channels configuration for PWM mode.


Build regular expressions piece by piece using human readable code. This package contains core functionality, and is primarily intended to be used by package developers.
| Version: | 0.0-3 |
| Depends: | R (≥ 3.1.0) |
| Imports: | stats |
| Suggests: | stringi, testthat |
| Published: | 2017-04-25 |
| Author: | Richard Cotton [aut, cre] |
| Maintainer: | Richard Cotton <richierocks at gmail.com> |
| BugReports: | https://github.com/richierocks/rebus.base/issues |
| License: | Unlimited |
| URL: | https://github.com/richierocks/rebus.base |
| NeedsCompilation: | no |
| Materials: | README NEWS |
| CRAN checks: | rebus.base results |
| Reference manual: | rebus.base.pdf |
| Package source: | rebus.base_0.0-3.tar.gz |
| Windows binaries: | r-devel: rebus.base_0.0-3.zip, r-release: rebus.base_0.0-3.zip, r-oldrel: rebus.base_0.0-3.zip |
| OS X binaries: | r-release: rebus.base_0.0-3.tgz, r-oldrel: rebus.base_0.0-3.tgz |
| Old sources: | rebus.base archive |
| Reverse imports: | rebus, rebus.datetimes, rebus.numbers, rebus.unicode |
Please use the canonical form https://CRAN.R-project.org/package=rebus.base to link to this page.


To cut to the chase, you can:
What is an F99/K00 Fellowship?
What RFA I used: RFA-CA-19-057From the RFA I used for my application:
The purpose of the NCI Predoctoral to Postdoctoral Fellow Transition Award (F99/K00) is to encourage and retain outstanding graduate students recognized by their institutions for their high potential and strong interest in pursuing careers as independent cancer researchers. The award will facilitate the transition of talented graduate students into successful cancer research postdoctoral appointments, and provide opportunities for career development activities relevant to their long-term career goals of becoming independent cancer researchers.
Essentially, the point is to provide funding that keeps graduate students in the academic pipeline. The natural (or at least, encouraged) next step/assumption is that you will apply for the K99/R00 funding mechanism. At least, that is my understanding. But this also gives you a lot of opportunities for your next stage as a postdoc since you will be coming into your lab already paid for for the first 4 years. Since you must first be nominated by your institute, the amount of work needed to give this opportunity a shot is definitely worth it. You write a letter of intent, if you are selected, you have a reasonable shot and you put in a lot more effort. If you are not selected, you only spent time writing a 1-2 page letter of intent.
To bring up the stereotypical quote for something like this, ...
My Previous Experience Applying for Fellowships
Before I applied for the NCI’s F99/K00 fellowship, I had previously applied for the NSF GRFP and an NIH NIDDK F31, both during my 2nd year of grad school. Both applications were unsuccessful. I think a few of consistent pieces of feedback I got for both applications were:
- The research ideas were good but not thoroughly thought out.
- The reviewers were not impressed with my training and career development plans.
- The reviewers were concerned about my advisor’s ability to provide mentoring due to their busy schedule.
- In each application, my undergraduate grades were brought up. This was a frustrating point to me because during my undergraduate studies, I was involved in lab research and enjoyed the research aspects much more than actual classwork. As a result, my grades suffered (many C’s, failed OChem). One important point that my advisor made though in response to this, was that once I got a publication out, reviewers would stop bringing up my grades (which is true).
While these were not successful, I do think that applying for these previous opportunities before the F99 was important and helpful. Writing an F-series fellowship application is a huge undertaking and given the timeline I was under for the F99 application, it would have been crazy to be writing my first F-series fellowship application for the F99. And for context, my impact score was 53 on my original NIDDK F31 application. During the time between my unsuccessful GRFP and F31, I did successfully get funding through an NIDDK T32, with the focus being “Computational Approaches to Diabetes and Metabolism”.
Getting Started: Submitting my Institutional Letter of Intent
I had previously discussed with my advisor my interest in applying for the F99 fellowship, especially as I had a friend in grad school who was awarded the F99 two years before, and a post-doc in our lab was on the K00 portion of their fellowship. For whatever reason, I did not find out about the institutional competition for the F99 application until Nov 7, 2019, and the internal application was due Nov 14th. Whoever was selected then had to submit their full F99 application by Dec 4th ( ❗ – so in my case, it was really fortunate that I had already applied for an F-series fellowship before and had started a new F31 application a few months before). Luckily, the internal application was pretty straight-forward as the only documents requested were my NIH Biosketch and a Letter of Intent.
By this point, I had already completed my first publication from grad school, which had been posted on bioRxiv, and we had just submitted the revisions for this paper to the journal. I had also participated in a couple of collaborative projects with several that were either already published or undergoing revisions with a journal. In my Letter of Intent, I made sure to emphasize these publications. Another big point I tried to sell was how my research was interdisciplinary – where I utilized mostly computational approaches to solving metabolic questions, but at the same time collaborated closely with a lot of wet lab biologists. At the time, I believe the NCI had recently announced some of their dedicated initiatives for Big Data in Cancer Research, which was another point I tried to emphasize here.
Writing my Application
On Nov 15th, I received the news that I had been selected to be the University of Utah/Huntsman Cancer Institute’s applicant for that cycle. Which was exciting, yet horrifying, since that meant I had just about 3 weeks to get everything together and submit my application. On top of all of this, I was going to be out of town Nov 18th - Dec 2nd for a conference and then a vacation right after with my partner and her parents. Fortunately, my original plan had been to apply again for an F31 during the Fall of 2019, so I had already begun this application to some extent.
Immediately after I found out I was selected, I emailed my letter writers for letters of recommendation and reached out to the post-doctoral fellow in our lab and the other graduate friend, and they were gracious enough to send me their F99 applications to use as guidance. I had also previously read Jean Fan's excellent blog post outlining tips and tricks for the F99 application. Additionally, Dr. Fan's application can be found on the linked blog post, as well as a link to Open Grants.
Another initial step I took when I started writing my F99 application was to re-read the reviews from my previously unsuccessful F31 application. As I already outlined above, there were some particular points of feedback that stood out to me from my previous application and, luckily, point #4 from above was taken care of as I had a first author publication in the works. To work on the remaining points listed above, I focused on three “lines of attack” for preparing my application:
-
Emphasize points of interest for the funding agency
Obviously, it needs to be clear to the funding agency that funding your research will advance their goals. To address this point, I tried to emphasize in each document (cover letter, research plan, training plan, etc.) that my research was interdisciplinary and would produce valuable tools and research that would help us better understand the complex systems of cancer metabolism. I also made sure to emphasize that while cancer metabolism is a very established field, a huge hurdle to accelerating advances was a lack of computational tools for analyzing these data, and pointed out a semi-recent review by Ralph DeBerardinis and Navdeep Chandel (Sci Adv, 2016) that made this point clear. I also made sure to mention my co-mentor’s expertise in computer science and network modeling in nearly every section of my application (take-away: any points you want to emphasize in your application should be mentioned in every section of your application where appropriate). Make sure your reviewer's remember those points!
Another point I wanted to emphasize based on previous feedback was my mentor’s ability to provide mentoring based on the “large group of trainees working in the lab”. This point I tried to emphasize mainly in my training plan.
I am extremely fortunate to work in Dr. Rutter’s lab, where I am given a great amount of trust and independence with my project and the its direction. I meet with Dr. Rutter one-on-one once a week to discuss ideas and experimental plans, and also frequently in person or via email other times throughout the week. Dr. Rutter has always provided prompt feedback that has been invaluable as I develop my projects. Dr. Rutter has truly become a mentor in every sense of the term, and someone I have learned from immeasurably. I also meet with the Rutter lab Big Data group every week to discuss the ideas proposed in this application and their progress. I am also able to provide feedback for my peers in this venue. I present my research often in lab meeting to get feedback on the direction of my projects. These meetings have been consequential to the development of my ideas as the members of the lab come from diverse backgrounds and have valuable perspectives. Additionally, I have cultivated a network of computational biologists at the University of Utah and often reach out to them with questions. The University of Utah has a strong collaborative spirit, therefore when my established network is unable to provide the necessary guidance, it is easy to reach out to someone with the necessary expertise at the University and they have always welcomed these interactions. For example, before presenting my research to a more computational audience, I meet with this network to hone my presentation for scientists from a computational background. Not only do these interactions help improve the research that I perform, but they also provide me with training to present my ideas and results in a concise and clear manner and defend those ideas in front of experienced graduate students, postdoctoral fellows, and senior scientists.
I also tried to emphasize my collaborator network and the feedback I have been able to receive from them to supplement the training from my advisor.
-
Organization/readability
Another theme from my previous application that I felt was common was the lack of clarity. Sure, I thought I had been clear, but I know what I am thinking and the context behind my thoughts, so obviously what I thought was clear was not. In looking at a friend’s successful F99 application, one striking pattern I saw in their application was the usage of tables and sub-section headers. With this in mind, I tried to make my Training Plan very organized and succinct, using headers such as “Research Development”, “Computational Training”, “Science Communication”, “Leadership”. I feel like this helped my overall organization of thoughts and ideas, and even if something was not totally clear to a reviewer, the theme was there underlined and in bold. I also included a table of my timeline and the milestones I wanted to reach during my training. I maybe also overused bolded text, but I do think it really helps emphasize the important points I wanted to make in my application.
-
Feedback
The final concrete theme I want to emphasize in preparing my application was getting feedback. This was particularly important given the accelerated timeline on I was on in preparing the application. In all, I think I remember three people giving me feedback on my Research Plan: 1) the post-doc in our lab on the K00-phase of their fellowship, 2) a fellow graduate student who was most familiar with my research and could make sure the key tenets of my project were clear and well-thought-out, and 3) my partner, who coincidentally is also in the Rutter lab.
-
Other
Another interesting point of concern in preparing my application was that I might be emphasizing my collaborative project too much. I think luckily more and more people are recognizing the importance of collaborative research more and placing less emphasis on “genius science”. My advisor let me know though that this is potentially a point some reviewer could view as a weakness. Thus, I made sure to emphasize this point in my Training Plan with the following:
In addition to the papers I will publish as first author, and to make full use of my unique background in computational metabolism, I plan to work on 2-4 collaboration projects per year that will lead to additional coauthor papers. While I have been able to contribute significantly to each of these projects, it has not deterred me from maintaining a high level of productivity on my personal projects.
And,
Make sure you follow the Fellowship (F) instructions in the SF424 (R&R) Application Guide. Read through every section and make sure you have formatted everything correctly, included all the information asked for, and so on!
Hopefully, these points are useful and give an alternative perspective to someone considering applying for an F99 fellowship. Particularly, it is low-cost to write a Letter of Intent for your institutional competition (assuming that is all they require in addition to your biosketch) and if you are selected, there is a relatively reasonable chance to be awarded the fellowship since you are only competing against one possible applicant from (in the case of the NCI) around 70 NCI-Designated Cancer Centers.
You can access my application here.
Application Feedback and Waiting for the Final Notice
So, long story short, I submitted my application in December 2019 and then waited. And waited. And waited. Also, a few months after my application submission, the COVID pandemic hit, and so then I had questions like “are they going to cut funding?”, “is this going to complicate the review?”, etc. I probably checked eRA commons hundreds of times. Finally, reviews were released April 22, 2020 and I received my Notice of Award July 22, 2020 with a start date of Aug 1, 2020. And to be honest, I don’t know if this is the general timeline (like getting no other indication of the award until the NOA a week before the start date) or if this was a delayed timeline due to all things COVID.
For my F99 application, I got an impact score of 19 (a big improvement from 53 from my previous F31!). It definitely wasn't a perfect application, and some of the same issues I ran into earlier were mentioned, but but instead of all of the reviewers bringing something up, usually only one reviewer would mention a given weakness and didn't seem to emphasize the point too much.
Overall Timeline
Institute LOI Deadline: 11/14/2019Application Submission: 12/04/2019
Reviews Recieved: 04/22/2020
NOA: 7/22/2020
Start Date: 08/01/2020
Conclusion
I know this is a case of survivor bias, but you should apply! It is definitely worth it, and you never know what will happen! I definitely thought it was a long-shot, but I'm glad I did it. And I know a lot of people with F99's that had previously received an F31 beforehand, but that is not always the case! I definitely didn't have one, and I know of others personally who didn't have one beforehand either!
Read: I still have no clue what I'm doing...
Let me know if you have any questions! I am happy to answer application-related questions, and, based on schedule, review parts of your application if you decide to apply and want some feedback. You can email me (maybe add a subject line of “F99 question” or something to make sure it doesn’t get lost in my inbox), and feel free to pester me if you don’t hear back.


Bam. And that's only scratching the surface. The reduce method signature is pretty complex: reduce<U>(initial: U, combine: (U, T) -> U) -> U
. The return value of reduce
is the same type as the return value of the closure and the first parameter. It also is the same value that is passed into the closure. Say we want to just grab the oldest person's birthday, but we don't care about the actual Person
object – we just want the date. Well, reduce
is such that we can do that.


S1 Fig
Anti-KSHV activity and cytotoxicity of histamine receptors antagonists. The lytically-induced iSLK.219 cells were exposed to different histamine receptors (H1R-H4R) antagonists, then their antiviral activity and cytotoxicity were measured as described in Methods. Error bars represent S.D. for 3 independent experiments. (TIF)
Click here for additional data file.


I wanted to incorporate Jordan Dobson's great Material Design Pointer module that determines the x and y coordinates of touch events. I aslo wanted to emulate the micro-interaction show for only one second at the 0:08 mark of this video teaser of Material Design.
View PrototypeAnother trailing circle but done in a different way. This time a target cirlce is added, which made the animating a lot easier. Drag the green circle to view the trailing effect, release to view the exploding sun.
View PrototypeAnother project is picking up steam so I've done only a small prototype today. I found that the TouchMove function is not working on mobile for some reason. After a bit of searching I landed on this answer on Stack Overflow. Based on it I built a trailing circle prototype. Touch and move anywhere on the screen to view it. It's a bit choppy, but I've already thought of a better way of building this, which I'll do tomorrow.
View PrototypeAgain keeping it simple today. I wanted to create a sticky header on scroll. Initially I tried to move each header label out of the scroll element as they moved past the top. Turns out it returns a nasty NotFoundError: DOM Exception 8 -- something about the target element not existing. I switched to setting the opacity of each layer to zero as it reached the top and setting the opacity of a hidden fixed background layer to 1. It did the job.
View PrototypeKeeping it simple for today's prototype. I wanted to recreate Safair's switch between opened webpages interaction. Turns out the built-in rotation functions are pretty handy for that.
View PrototypeFor today's prototype, I wanted to recreate the lock screen experience on iOS. This is largely a re-do of Jorn van Dijk's great example on FramerJS gallery.
View PrototypeI wanted to recreate the quick and subtle zoom animation on app launch and minimize. What makes it interesting is the animation for folder, which adds an zoomed level between the home and the app screen. Tab any icons to view effect.
View PrototypeThis prototype needs to be viewed on a mobile device. The pinch to zoom interaction can only be demo'ed there. I was trying to build something similar to the iOS Photos app. This prototype is still quite buggy. The video tutorial by Jay Stakelon and the FramerJS gallery prototype built by Benjamin den Boer were quite helpful.
View PrototypeContinuing on the success of iPad video scroll pause prototype, I decided to prototype a video preview idea where the videos auto-play based on scroll position.
View PrototypeToday I decided to emulate the transition interaction on New York Times' VR app. In a feed of VR experiences, when the user clicks on one of the experiences, the background images takes over the entire screen and the user is presented with the option of viewing it in Google Cardboard or on their Smartphone. In donig this prototype, I learned about string interpolation in Coffeescript and the differences in Chrome and Safair rendering.
View Prototype


new BindingBase(observer)
| Name | Type | Description |
|---|---|---|
observer |
Observer | optional Optionally provide observer on construction. |
Methods
-
onRun(value)
-
Called when BindingBase#run is finished
Name Type Description value
? The value returned from BindingBase#run -
onStop()
-
Called after BindingBase#stop
-
run()
-
Called in the context of the observer's proxy
-
runTracked()
-
Calls BindingBase#run and tracks dependencies
-
start()
-
Calls BindingBase#run and starts listening to observer
-
stop()
-
Removes any active listeners
-
withOnRun()
-
Builder pattern for BindingBase#onRun
-
withRun()
-
Builder pattern for BindingBase#run


When we shine light through a prism, it is broken into its component parts and we would see a spectrum. There are three different types of spectra (see Figure F-2-3):
1. Continuous spectrum – produced by a hot and dense energy source. Examples are cores of stars, incandescent light bulbs, any opaque objects that have some temperature. In Astro 1 we referred to these objects as having thermal radiation which we represented by blackbody curves. From the figure, you can see that a continuous spectrum can be described as all colors of the rainbow, or a black body curve.
2. Emission spectrum – produced by gases and transparent objects. Examples are gaseous nebula in the Milky Way galaxy, a neon light bulb, or any excited gas. Emission spectrum consists of bright color emission lines overlaid on a black background.
3. Absorption spectrum – is a combination of the previous two. We see an absorption spectrum when we are looking at a continuous source through some gas that is cooler than the continuous source. See Figure c bellow. A real life example is a spectrum of any star. Stars have hot dense cores that produce uninterrupted continuous spectra but their photospheres (upper layers) consist of a cooler gas that absorbs some of the light from the core. This absorbed light looks like dark lines on top of a continuous spectrum.


Our success to date is based on having great people who are passionate, focused, hardworking, innovative and fun. We band together to support each other, our customers and most importantly help each other grow.
Our platform represents a solid foundation for your healthcare business to connect safely, seamlessly and privately with referral programs and remain agile and adaptive to an evolving healthcare system and consumers needsy.
Client’s know when your practice is running smoothly & efficiently. Take advantage of cloud-based technology to empower your daily workflow and improve client outcomes with smarter online software.
A 24/7 Support Center and backed up by our very own customer chatbot Corey, our users are always guided to a way forward and provided a solution to any issue that may arise when operating their practices via coreplusy.
We are a passionate team that believes every health professional in Australia deserves to practice happy.


WITNESS LIST Licensing & Administrative Procedures Committee April 14, 2003-8:00A HB 656 For: Hopkins, Gay (Self) Niemann, Larry (Texas Building Owners & Managers Association) HB 1615 On: Kuntz, William (Texas Department of Licensing & Regulation) HB 1620 On: Combs, Susan (Texas Department of Agriculture) HB 1759 For: Ellison, Albert L. (Self) HB 2062 For: Johnson, Joe (Association of Texas Career Counselors) Mintz, David (Texas Apartment Association) Niemann, Larry (Texas Building Owners & Managers Association/Texas Mini-Storage Association) Against: Brannan, David (Austin Lawn Sprinklers Association) Salas, Gary (Self and Austin Lawn Sprinkler Association) Schwartz, John (Self and Texas Turf Irrigation Association) On: Batterton, Carol (TCEQ) Cranston, Ron (ADAPT) Hassumani, Sabrina (Texas Real Estate Commission) Kuntz, William (Texas Department of Licensing & Regulation) Wittie, David (ADAPT of Texas) HB 2593 For: Elliott, Gary (Self) Parker, Gabe (Self) Puente-Brancato, Gina (Texas Wine & Grape Growers Association) Switzer, Cord (Self) HB 2793 For: McGlothlin, Sandra (Self and Roofing Contractors Association of Texas) Against: Ornelas, Sergio (Hispanic Contractors Association) Pearson, Stacy (Roofing by Stacy Pearson, Inc.) HJR 85 For: Elliott, Gary (Self) Parker, Gabe (Self) Puente-Brancato, Gina (Texas Wine & Grape Growers Association) Switzer, Cord (Self)


I am a PhD student in Computer Science at McGill University and Mila co-supervised by Prof. David Meger and Prof. Doina Precup. I am also working with Prof. Prakash Panangaden.
My research focus is on temporal and state abstraction in reinforcement learning, particularly for continuous control problems. During my MSc, I worked on data-efficient methods for learning robot dynamics for control and interaction inference.
AI4Science
Meta imitation learning and meta reinforcement learning for continuous control and robotics
Multimodal generative modeling for learning intuitive physics using the senses of touch and vision
Deep reinforcement learning for automated video game testing
Object detection neural networks for human hand-wave motion detection
Conferences and Journals
Workshops


{{progress}}%
Bio
then a title
No Rating Available
Hourly rate
$30
Profile text here
Select
Bio
then a title
No Rating Available
Hourly rate
$30
Profile text here
Select
×
Confirm
You are about to choose
Name
Write the rationale for it!


Craigslist redesigned to be tailored towards students buying furniture.
Link to interactive prototype:https://projects.invisionapp.com/share/JQAGBGKN3
To get initial idea of how Craigslist works, I navigated through the website, inspecting its features and flows.
Link to feature analysis:https://docs.google.com/document/d/14B9zeo_uD_8TLmFWLd-cfSaKHOa7I25MNx7XtV1mwbQ/edit?usp=sharing
Additionally, I conducted a brief competitive analysis with Etsy, OLX, Kijiji, and IKEA.
Link to competitive analysis:https://docs.google.com/document/d/1vpTpNsCsAgKniWvKQ5vwKEaJjcYKwIfo-o_si_a6OZg/edit?usp=sharing
In order to get insight into Graigslist and how students use it, I conducted interviews with 3 students. From the interview, I got insights into problems, such as:
In parallel with the interviews, I also gave the students teh task of 'buying a table' on Craigslist. I observed their behavior and the thoughts and challenges they had with the task. Here are some things I learned
Once I got a sense of direction from the qualitative research and evaluation, I conducted a survey to attempt to validate some ideas and get better sense of the population.
I received response from 67 people, many of which were students.
Link to survey results:
The survey reviewed some of the following insights
Based on the results, I started sketching potential prototypes
Finally, I created a digital prototype using Sketch and InVision
https://projects.invisionapp.com/share/JQAGBGKN3