Day 6

My experiment has officially started! I first cleaned up the code and prepared it for the 24 test cases, with 30 trials each. Then, I ran it. And waited.
...
I predict that this will be a common trend for the next few days.
During my downtime, I wrote my abstract and read some papers about machine learning models. The first test finished just after I came back from lunch. After collecting the results and calculating the relevant statistics, I started the second test. It was some time after this that I became aware of the fact that I was using 100% of the memory of all four GPUs on the server. After promptly stopping the experiment, I changed a setting to minimize the damage to only one GPU and started it back up. Luckily, the program's performance didn't change significantly, since some packages like to allocate memory it doesn't necessarily need (hence why it was happily devouring ~48000 MiB). I've been running the experiment remotely since I came home, and I plan to leave it running over night. It shouldn't be too far of a stretch to have all of the data by next Monday.
That is if nothing goes horribly wrong.

Comments

Post a Comment

Popular posts from this blog

Day 31

Presentation day! I'll admit that I was pretty nervous before going up to present. There wasn't much reason to feel so pressured, but the other interns did so well, so it felt like there was a standard to be met. As per tradition, my presentation was under time, even though it was over time when I was rehearsing the night before. Not a big deal. My biggest concern going into today was that nobody would understand what I was talking about. After presenting, I still got the feeling that nobody understood what I was talking about. I guess I'll never know for sure. Dmitry did ask a good question though (to which I provided a mediocre response), so I suppose that proves something. I think all of the interns did really well today, and this was a great way to end the internship. Postmortem time! Coming into this internship, I had nagging doubts about the program, most of which, to be honest, revolved around it being unpaid. These doubts were first addressed on the day of my
Read more

Outline

Motivation/Background: HSI classification What is HSI? Comparison to RGB The advantages of HSI over other kinds of data Instant, remote, nondestructive data collection Hundreds of data points per pixel What is classification? Introduce using toy data set, like CUB-200 Applications of HSI classification Cancer detection Art authentication Food quality analysis Remote sensing Urban development agricultural monitoring environmental assessment Problems faced High dimensionality Scarcity of labeled data Method: MCAE and Ladder Network Feature Extractors Baseline: PCA Inspiration: Autoencoder Our proposed method: MCAE Classifiers Baseline: SVM Inspiration: Neural network Our proposed method: Ladder network Results : State-of-the-art Comparison Comparison of MCAE against PCA and state-of-the-art Comparison of Ladder Network against SVM and state-of-the-art
Read more

Day 2

Day 2 started with a very brief meeting where we went over the schedule for the next six weeks. Abstract, outline, presentation; two weeks per task. It was at this point that I realized the difficulty of making technical topics sound interesting, then I immediately dismissed the problem as one for my future self. Today was dedicated to Support Vector Machine (SVM) creation, evaluation, and optimization. I was unaware of many of the wonderful functions included in the provided libraries, and ended up doing the data reformatting less elegantly. It still worked, so I left it. When I finished up my SVM code, I tried to help Nate with the errors he was running into. The keyword here is "tried." Note that it's not easy to explain concepts that you figured out hours earlier and happen to be more complicated than they should be. Nate was a good sport about it though, and with Ron's help, he had a good idea of the solution by the end of the day. For the last part of the day,
Read more