Formally relinquishing timeline format and utilizing progress notes, with simple -‘s and spaces
Week 2: I work on making sure the code will be successfully executed and works.
Week 1: I am sick for a week
Week: 4 I work on SSH and successfully SSH.
Week 3: I study the logs detailing the process of the original team, and see if there are any problems I should face.
Week 2 : I successfully download operate VNC work on getting accustomed to the files and code.
Week 1: I start downloading and utilizing VNC viewer and a SSH tool, in order to be able to access the NUC at any time.
Week 2: I work the on the Booting order of the NUC due to some problems. In addition, I start working more on Exoplanets and their properties, due to my intrest.
Week 1: We discover and use a battery the the previous team used, successfully booting up the NUC
Week 3: Poster Session occurs, I start working on more relevant code beforehand.
Week 2: I finish up my Poster.
Week 1: Informed of the Poster session, so I research my topic furthermore, and start on my poster.
Week 3: Continued issues, but development within the setup of the NUC, such as automatic booting up after a power outage.
Week 2: I(Colin Fields lefts the project at this point) power the motherboard, but there are malfunctions with booting up ubuntu on the NUC.
Week 1: We start working on the power system of the Telescope, due to the 12V and 3.4 amp power system for the Computer(referenced as NUC in the future).
Week 3: Discussions
I contact my parter, Colin Fields, and educate myself on what I am working on.
Week 2: Development
This is the time when I have to decide what I want to do, and I see PANOPTES, in which we are working with CalTech to create a telescope.
Week 1: Introductions
Beginning of the Year, I start with the Glowforge- a laser printer utilized in imprinting wood.
Ubuntu won’t load
– Changed boot-load order
– wont boot up main page anymore
– attempting to reset boot-loading order
– power fixed
– losing issues after booting malfunction
– using 12V battery
– coding may require updates
– work on Ubuntu coding
– “Connection Refused”
– Timed Out
– Plug in and Charge Battery
– connect through the monitor, mouse, and keyboard
– Check things such as ssh, housetop, eat
– problem found in the lack of a ssh server
– most likely due to update of Ubuntu
– new update available
– update now, as to not have to download servers again, and download OpenSSH servers later
– Error saying “Problem in software, log in again”
– Turn of N.U.C
– Blinking text cursor in the top left
– No input works
Step By Step Basis
Alt, Tab, F4
sudo apt-get purge lightdm sudo apt-get update sudo apt-get install lightdm dpkg-reconfigure lightdm
Sudo shutdown -r
You can and now to then end(-r now) to do it instantly
-Log Back in
SIGNIFICANT NOTE: A file with information of paramount importance can be found on PANO_15 UnitOn the Panoptes folder there is a file called README.rst, which gives coding information on how and what to download, utilize, delete, ignore, ect. In a concise form, make sure to check the README.rst file.`
SIGNIFICANT NOTE: Make sure to update as many times as possible, as on update will not update them allUpdates are performed through the usage of the “Software Updater” app, and require admin access(WISRD Password)
SIGNIFICANT NOTE: Make sure to be attentive to the interface, as it often requires passwords, restarts, or interferenceUse google or a trustable online tool to download or enable content for Ubuntu, such as in Problem 4
– Can’t access OpenSSH through “ssh localhost”
– Downloading OpenSSH after numerous updates does not work