OpenMRS Radiology: Finished Issue

My group was working on an Issue ticket, RAD-159, where we had to delete unused code in two files. It appeared to be a simple task at first, but through a lot of confusion, we had to redo our deletions multiple times. The tickets description of what to do was not specific enough, and even after asking for help, we were still confused. This shows how important clarity of instruction is when designating work to other people. This ticket should have taken a day at the longest, but it was extended for long periods of time due to having to ask numerous questions and then having to get our group together after each answer. We did finish our issue though, and we are hopefully going to have our revisions accepted. In the future, I will know to be as thorough as possible when writing directions for other people.

From the blog cs-wsu – mmoussa7wsu by mmoussa7 and used with permission of the author. All other rights reserved by the author.

Posted in cs-wsu | Comments Off on OpenMRS Radiology: Finished Issue

OpenMRS

OpenMRs

I spent the last week to reinstall Vagrant and OpenMRS radiology module. Because they didn’t work properly. Our professor made a very good tutorial about how to setup everything. I deleted Vagrant and OpenMRS modules, and reinstall all of them based on the tutorial, and finally everything worked correctly. This week we were working on the RAD-138 issue, and we made some changes to some messages. Then we updated the radiology module. But right now when I test the radiology module it doesn’t work, and I am trying to fix it.

From the blog cs@Worcester – siminshamsblog by sshamsfallah and used with permission of the author. All other rights reserved by the author.

Posted in CS@Worcester | Comments Off on OpenMRS

OpenMRS: A New Issue

This week couldn’t have gotten any better. We’re already working on another issue, coded RAD-235.

On Monday, we found out that our original issue, RAD-58, was already completed by Ivo, one of the lead developers of the OpenMRS radiology module, but he forgot to mark the issue as such. As a result, Ivo granted us another error that he knows he never worked on.

We made progress on this issue since Wednesday, and there’s still more to be done with one week left. Although one of our group members couldn’t understand how the enum class in Java worked. We’ll see if he can figure it out by next week.

From the blog cs-wsu – jdongamer by jd22292 and used with permission of the author. All other rights reserved by the author.

Posted in cs-wsu, openMRS, radiology, software | Comments Off on OpenMRS: A New Issue

Finally

Well, my first pull request was a bust. Obviously it would be since I didn’t adequately test it, but I finally got everything resolved and have my test environment set up correctly… Sourceforge seemed to be the common point of failure during my dozen or more vagrant up attempts. The dcm4chee dependencies are hosted on Sourceforge, and it consistently timed out, or errored out when trying to retrieve the zip files during the vagrant up process. I eventually got lucky on one attempt before I was going to try to vagrant scp the files onto the VM and see if I could get it working that way. I’m finally ready to test and will keep everyone updated:)

From the blog cs-wsu – spencerleal by spencerleal and used with permission of the author. All other rights reserved by the author.

Posted in cs-wsu, CS@Worcester | Comments Off on Finally

PAX East 2016: VR in a Software Development Environment

This year, I went to PAX East in Boston. At least one exhibit I saw on the show floor contained at least one VR (virtual reality) device to try. During the event, I had the chance to try the Oculus Rift and the HTC Vive.

On Friday, the first VR project I got to see was an Oculus Rift story told by a WPI graduate. “The Piper” tells the ancient story of the Pied Piper of Hamelin in a first-person perspective. Although the sequence through the Oculus Rift headset was accurate, I found some bugs. For example, several of the virtual children kept passing through me as if I wasn’t there. This was something I could expect from an early use of VR.

I never got the chance to try any VR related projects on Saturday, as I was focused on other independent video games. Although on Sunday, another opportunity to try VR arose with another project from an independent Chicago-based developer. Titled “We Are Chicago”, the game tells the true story of a family the southside of Chicago, historically a part of the city where most gang violence has happened. In the demo, the family, the subject of the game, goes through their normal evening routine when gunshots are heard. It is then the player’s choice to take the story in their own direction. The booth displayed an HTC Vive setup, allowing the player to control the character using the headset and the two handheld motion controllers. During a brief interview with Lead Designer Cindy Miller, she told me that the game was not meant for VR and “because you’re in a Virtual Reality setting, you are expected to have unexpected things happen, like going through a table or a counter.” This had happened to me many times in my experience with the demo, though they didn’t give me any problems as I was able to fix my position easily with a combination of moving myself and the use of the motion controllers.

After the event, I looked back at a panel that was in progress while I tried We Are Chicago. The panel, “The Cutting Edge of PC Gaming with Newegg,” centered around the future of VR as well as the relationship between hardware and competitive gamers, a concept collectively known as eSports. The entire panel focused on a hardware developer’s perspective on how VR is affecting the consumer base. Several key points were made about VR, including its impact and whether it was here to stay. When asked about impact, and using education as an example, Robert Hallock, Head of Global Technical Marketing at AMD, stated that VR “redefines the way [anyone] can sense and understand learning,” supporting his case with examples such as the ride of Paul Revere and a child’s perspective of a blue whale swimming over their head.

In my perspective, I think VR has a place in the software development environment for many reasons. One of them is the many opportunities it brings, such as the point about education that Hallock described in the panel. In the same panel, when asked whether VR was here to stay, Hallock stated “versus 3DTV…everyone [he] talked to has tried or wants to try VR.” Chris Pate, Senior Product Manager at Logitech, described the evolution of VR before Hallock, stating, “as [VR] becomes more immersive [and] more compelling…that’s where it drives the interest…of the technology and…the accessibility and affordability of it is a large part of it.” These statements have helped me push my stance towards the inclusion of VR in the software development field, and, taking in a quote from Chris Geiser, Head of US SSD Sales at Samsung, I “certainly think that [VR] is a technology that is here to stay.”

You may watch a recording of the hour-long panel on VR here:
https://www.twitch.tv/pax3/v/62558539

From the blog cs-wsu – jdongamer by jd22292 and used with permission of the author. All other rights reserved by the author.

Posted in cs-wsu, pax east 2016, software, virtual reality, vr | Comments Off on PAX East 2016: VR in a Software Development Environment

My Very First Pull Request

We worked on the issue RAD-138 and we finally made our first pull request! Initially I had tried cloning from https://github.com/openmrs/openmrs-module-radiology/, and setting up two remotes, one for our team, and one from the base repository. My goal was to be able to pull from the main repository, and have our team push and pull to the cloned version I created. This worked for those purposes, but I had some difficulty squashing commits into a single commit due to me merging the OpenMRS master into our branch between doing work on the code, and work on the related tests.

I realized after struggling with squashing commits that I needed to fork the repository to send a pull request anyways, so I forked the repository and cherry-picked my commits from my previous branch, squashed them, and pushed them to a new branch on the forked repository. I learned a lot about git rebase, git cherry-pick, and how pull requests work in the process. It would likely have been tremendously helpful if I had actually read The OpenMRS Contributing Guide before beginning, as they explain how to set up the repositories, and use git pull –rebase to more easily squash commits, but I think learning more about git hands-on was incredibly beneficial.

I hope our pull request gets accepted and will let the world know:)

From the blog cs-wsu – spencerleal by spencerleal and used with permission of the author. All other rights reserved by the author.

Posted in cs-wsu, CS@Worcester | Comments Off on My Very First Pull Request

Post from week 4/25-4/27

This week we finished RAD-58 and found out it had already been completed so we started RAD-235. This issue has to do with the modality of the radiology machine. Ivo wants them called a different way. On Wednesday we believed we completed the issue. On Monday we will discuss as a group if we think our issue has been solved. If we agree that it has been we will send a pull request and submit our solution. Hopefully it will be accepted. I am assuming that if it is accepted or while we are waiting for it to be accepted we may start on a new issue if we determine we have enough time.

From the blog chanson2016 by chanson2016 and used with permission of the author. All other rights reserved by the author.

Posted in CS@Worcester | Comments Off on Post from week 4/25-4/27