The Week 6

Greetings,

We met twice last week (Thursday and Monday) because the mentors suggested some changes to the code last Thursday, which I had to include by Monday. They also wanted to go through the code and do some refactoring.

Matthias proposed an idea which would lead to complete backward compatibility for annotations, and would also not cause any information loss, a thing which I thought would not possible to achieve simultaneously. Here's the idea:
  • First of all, we are going to have a main Metadata class which is going to store all the meta-information like the external resources linked to that component (Controlled Vocabulary terms, or CVTerms), history of that component, and listofKeyValue pairs present inside the annotations, a feature introduced in FBA-v3. We are going to have classes for each of these three inner metadata information, and an object of each class inside the Metadata class.
  • The annotation of a component will be an object of this metadata class and you can access the information corresponding to the three classes via annotation.cvterms, annotation.history and annotation.listofKeyValue.
  • In addition to these, we are also going to have a private variable on this Metadata class (_annotation) which is going to store the data of external resources in the old format.
  • The data of cvterm and annotation will be synchronized between each other i.e addition of a new cvterm will lead to the addition of new resources (if possible, because not each and every resource URI satisfy the present regular expression syntax) inside the private variable annotation.
  • Now whenever a user makes a call to the 'annotation' object of the component, the data inside this private variable will be returned. This data may not be complete, but it will be in the old syntax.
  • And a user who wants to get the complete data can get it from the cvtemrs object present inside this metadata object.
I changed the code accordingly and Matthias reviewed and improved the code on Monday, and suggested some changes which I was required to make until Thursday. He also wrote a few simple tests, that needed to pass using the new implementation. I made the changes and everything worked well in the next meeting. I am still cleaning up the code, and have even opened an issue on my forked repo to keep a track of it. I shall now start with the reading and writing of models using this new format. Also, since I was unable to cover the parsing of notes information last week, I will target it this week. The phase-1 evaluation will start soon, and I would complete this part before that. This will also lead to the completion of Milestone-2.. Also, I was unable to cover the parsing of notes information, which I will target this week. The phase-1 evaluation will start soon, and I would complete this part before that. This will also lead to the completion of Milestone-2.

That's all for this week.
Thanks for reading.
Location: Rewari, Haryana, India

Comments

Post a Comment

Popular posts from this blog

The Week 12

Greetings, The last meeting was not too long, it ended in approximately 35 minutes. The mentors first went through the JSON schema-V2 to see the definitions of features added to JSON like group, user defined constraint, annotation etc. They suggested a few modifications like adding pattern properties for datetime and Id. The schema was otherwise all fine. After this, we started discussing the helper function for adding user defined constraints. I had implemented this method by parsing string by my own and extracting information out of it, which lead to various restrictions on defining the constraint. But Matthias suggested that the best way to handle expression inside a string is by using the Abstract Syntax Tree (AST). By using the tree, we can define our constraint expression more freely, with just a few restrictions. So I shall add this support using AST. The other important thing that we discussed was the JSON validation function. Currently, I was using the inbuilt JSON validation
Read more

The Week 13

 Greetings, Almost towards the end, we didn't have anything new to discuss in the last meeting, except the identifier (id) of COBRA model components. The 'id' of an SBML component is an important attribute and should not be manipulated. COBRApy, however, allows the user to pass a replacement function to manipulate the component ids. It also asks the user to pass a reverse replacement function to modify the ids while writing the model back. We discussed this thing and both of the mentors were having an opinion that ids should not be manipulated at all, it can create problems. Currently, the COBRApy writes the same manipulated ids in the JSON format, and if we apply the defined id pattern properties of SBML to these manipulated ids, these ids may get failed. So at the time of reading/writing the model from JSON, I have used the default replacement functions to fix the ids. Another thing which we discussed was the things which COBRApy communities have listed to port the code f
Read more

The Final Report

Image
Greetings everyone, I am glad to write the final report for the project "SBML-JSON converter and SBML scheme". It's been three months now since I am working on this project and about 5-6 months since I am involved in it. And I must say that I have learned quite a lot by now, thanks to Matthias and Andreas for all their help. It had been a very nice journey with both of them, marked by daily chats and weekly meetings.  We have actually covered all that we claimed in the initial proposal , and the complete code has been submitted to COBRApy . Two of our pull requests have got merged, one is under review and will get merged soon, and one may require some time because it contains some functionalities which will be used only after  libsbml (the interfacing library between SBML and COBRApy) incorporate fbc-v3 package.  All the pull requests submitted so far are summarised in this spreadsheet . Here is a summary of the work done in this project: The JSON schema v1 had some i
Read more