Starting over on the project with Swift instead of Obj-C
Whoops. It wasn't parsing the JSON string, so everything was fail.
Added update_visit function, modified list_visits to return all visits (and additionally, the visit ID) instead of 3.
Improved error-checking, several bugs (index out of range, mixed up logic, etc.) fixed, full functionality of visit notes added.
This version introduces the groundwork for making longer notes and view visits better. This feature is not yet functional.
cDashboard startup speed has been cut by an exponentially high margin. (In English:) The higher cStopwatch goes the slower the application would startup. Due to the way font sizing within labels is currently implemented, it still is sort of exponential, but at such a slow rate that I wouldn't be worried about elapsed hours up until at least 9999. It should work just fine after that too. I did this by changing the amount font size changes during every check from .0001F to .1F. Sort of a 1000x difference if you think about it.
This does come at a small accuracy cost, however with various cStopwatch times including my current 400+ hours, I couldn't notice the difference, so all is good. It really wasn't worth having the startup slow over this, or even sending it to another thread.
The faster we go, the harder it is to see. (I don't really know if that reference makes sense to anyone but me, but that's okay.)
Recently, I returned to working on media uploads, beginning with article photos. In an effort to make media uploads extendable, the database is seeded with multiple media types. So far, I've added media types for photos and XML files. Photos will be linked to articles on both the front page and on the article view page. XML uploads will be available for uploading and parsing entire articles. Any future media types will be easily added using this system, as opposed to creating an upload procedure for each new media type.
Link media uploads to articles. Support images on front page
Support images on front page
Added a nonworking feed page to view all compositions
Added a showing the database setup. Somewhat simple.
Now using the MIT license.
I found a few significant bugs over the last few days. The two big ones were my failure to convert units (which, if done properly, leads to over 4,000 times stronger friction than I had) and my confusion of ctx->timestep with st->step. I had needed timestep to determine where particles were last before they moved to their current positions so I could see if they went through any caustic rings. But since I used step (which records the number of times the simulation has moved a little forward, and gets big pretty fast), the "old positions" I was calculating very quickly became extremely far away and the angle the particles were perceived to travel through the caustic ring became relatively constant. And since the strength of friction is extremely dependent on the angle... well, that led to issues with dynamical friction too. Since then I've also switched over to a much better method of determining where the particle crossed the caustic so as to refine the angle even further. As an extra bonus, the new method makes it easy to calculate multiple passes through a caustic ring that happen during the same time step. The dynamical friction code can now be found in my github under "milkywayathome" since it's easier at the moment to do dynamical friction with milkyway@home. If you want to run the code yourself, you will need to clone the milkywayathome repository and put my milkywayathome files into the milkywayathome nbody/src subdirectory. And make sure to run it with nbody_cl off in the cmake options since I only rigged it to work for nbody_plain. I'm running fixed simulations right now, but I'm also about to do some testing on my angle calculations separately to make sure I fixed everything.
Fixed some simple formatting, more consistent
cWeather is a thing. It can get weather for a location, zip, city (comma) state. Or if you really don't know where you are, you can get location by IP. It is really cool. It auto updates every 2 hours. The user can also force an update whenever they want. It uses the Wunderground.com API.
I'm not going to lie, working with Android is a nightmare. The IDE Google provides is barely functional, the toolchain used to build the application is temperamental at best, and the ADT in general just shoves everything that Java does wrong down your throat. I've made progress, just very little. This project has been mostly a learning experience with a new platform that I can honestly say I've come to hate. If there are any experienced developers that want to take over the reins on this project...
Implemented inverse parabolic interpolation, a bisection method, as the optimization algorithm for the density profile.
RCOS presentations are an excellent wake up call. By presenting a demo of your software, you are able to see the audience's reaction, get feed back through questions, and hear any suggestions other developers may have. When working within the team, it's easy to get tunnel vision and loose track of what people actually want from your application.
After presenting, I've realized how important it will be to nail down the article submission work flow. Our current system is messy, to put it lightly. Supporting XML and/or InDesign file uploads will be extremely important because it will save our users considerable time, as opposed to converting their entire body of text to valid HTML formatting.
Looking beyond RPI, this project's success will depend on the customization features and clean user interface. For other schools to adopt this platform, it must be easy to deploy and easy to edit with their own logos and styling. Therefore, another important set of features to implement will be color scheme editing, website logo uploading, and editable page titles. Even more important, and challenging, will be keeping the UI organized enough so that people aren't confused and discouraged from using this platform.
Auto approve group memberships, article edit for owners and admins, sepa...
Whiteboard is now hosted on Amazon Web Services but I am working on getting static content to work correctly. None of the static content is working correctly.
Added Color Quality Scale (CQS) to my list of calculated metrics. I also fixed (again) the LUV color difference optimizer. Last but not least, I added a decent README complete with demo instructions to help people download and use the tool for the first time.
The last blog post was too generous - when you don't forget one of the factors in the equation as I had, even 400 km/s stops providing any noticeable dynamical friction. I also made the dark matter sheets sensitive to the angle that you pass through them... which seems like a pretty non-negligible oversight considering that the sheets effect you much more strongly if you graze them (if you were to graze infinitely thin sheets -absolutely perfectly-, then you should be infinitely influenced by them). But according to the simulations, it's very hard to graze them well enough for even that avenue to give you significant dynamical friction. I also decided to run some dynamical friction simulations where the friction was artificially pumped way up, just to see what happens. If you go in the direction of the flow, it blows you apart and scatters you outside the flow ring. But if you go in the opposite direction, it slows you down and you end up falling into the galaxy (and still scattering, though less so). Another, less pumped-up simulation is running right now, along-side a couple simulations that are more realistic. While waiting for all these simulations to run, I've been doing work on the presentation I'll be giving tomorrow.
Changed gridding for dob and dateVerified fields.
Some catching upSo, a lot has happened since Tuesday when I gave the final presentation for RCOS this summer. I was able to push the project through to pre-alpha for the presentation, but that left a lot of sloppy code behind that needed cleaning up.A Step in the Right DirectionSo a lot of internals were changed in the clean-up process. Roughly 40% of the code base was re-written, or edited. At the end of the process I ended up refocusing on the MapEditor, as it needed the most changes because o...
Reworking login, something was wrong and I can't figure it out. Also added css files that I forgot.
...and I've lost a lot of hair trying to figure out how the heck to use an external library with it so I can parse PDFs (see the last blog post). For the sake of my mental health, I'm setting .pdf functionality aside for the time being, and am happy to announce some other progress: Text file functionality!
SpritzReader now has the ability to read files from external storage (SD Card) and display them in the application. However, the current text file location is hard-coded, so I need to implement some means of navigating external storage to read specific files as well. This is most likely what I will be working on next.
Text file in question is currently hard-coded, still need to implement choosing files and file navigation.
Scrollbars added, date-entry format changed (still shrinks too much when window is resized, so will probably be changed again), dateJoined and dateVerified added. Groundwork laid for gui color customization.
I haven't posted in a while, but I have been continuing with golang. I recently have been looking into sample projects that use martini or gorilla and learning the 'style' in which to write golang code. I am looking forward to working with go after the summer session is over and using it for other projects as well. The os/exec and net/http libraries are impressive.
parsing cut off midway and change is saved
files, removed Debug namespace from Pb
As our interest in home brewing beer continues to grow, we have begun work on the application! Our first brew is finally finished and we have a good grasp on the flow of brewing beer. The app is beginning to take shape!
Started working on Battle.
Also, returns 0 instead of null on unvoted videos