This is my weekly update on my Google Summer of Code project. There will be three parts of this blog post: what I did, what had issues, and what is next. Then, I will end it with a question that I need answered for part of the project.
Take a look at an example of the tours on YouTube.
Added overlay
Hello!
This week after fixing some issues of the developed score comparison engine (mostly concerning spanners handling) I have started a work on a graphical interface for the score comparison tool. Currently its look is far from perfect but to some extent it works. Below is the screenshot of MuseScore with the new tool launched, as it looks at the moment (full resolution):
[inline:Screenshot_20180716_023050.png]
During the next week I will improve the interface of the tool — hopefully
Read moreHello!
This week I have thoroughly tested 350 more scores, so now we are done with almost done with 520 scores from a bunch of 988 scores. There are some issues that I found which crashed the application so the XML generated were not complete and eventually, the OMR gave parsing error. There was no other issue than this which I found. Some new shapes again that are not annotated. I will be compiling them, posting them on the issue
This is my weekly update on my Google Summer of Code project. There will be three parts of this blog post: what I did, what had issues, and what is next. Then, I will end it with a question that I need answered for part of the project.
Expanded the tour framework
Hello!
This week I worked mostly on the score comparison engine which I have started to develop during the last week. Last week ended for my work on the project with a problem of getting a semantically correct diff between MSCX (or, more generally, XML) documents. This week I finished a work on correcting a usual textual diff to be more correct from XML point of view (mostly to contain a whole number of full XML tags, if possible),
Read moreHi :D
Week 8 is done and it was full of closely looking at the results generated using the XMLs generated. We have planned that we will chunk 988 scores into chunks of 150 to 200 scores and closely examine each segment so that by the time we are on the last segment, we will have everything sorted. I have shared some list of shapes on the issue tracker which are missing in OMR. I will keep refining our code
This is my weekly update on my Google Summer of Code project. There will be three parts of this blog post: what I did, what had issues, and what is next. Then, I will end it with a question that I need answered for part of the project.
Hello!
This weekly report will probably be not the longest one :)
This week after submitting the pull request on the first part of my work (which I mentioned in my last blog post) I worked on a new textual score comparison tool built in MuseScore. In fact, the only thing I have built into MuseScore to this date is just a console diff-like tool which is (usually) able to map the found differences to actual objects in the
Hi :D
Week 7 is over and we are into making things better and better, day by day. As discussed with Lasconic, I'm into testing now and discussing with Herve about the results that are generated for our test set of 988 scores. I have shared the test results with Herve, his review is crucial to better understand the requirements. Coming to this weeks analysis:
Below is the segmented status of the project:
Current status of the project
We are
Hello!
I seem to be a bit late with my post (well, I am definitely late) but I have a good news for now. After six weeks of work I could finally post a pull request with the proposed changes to MSCX fileformat. The list of changes itself can be found here. I am not sure whether this work was done fast enough or not, and I am sure that the issued pull request will require some more adjustments
Read more