Skip to main content

Week 3 :- CERN-HSF @ GSoC 2018

This week had the 'first deliverable' to be submitted. But not an easy task though. Even after coding and removing bugs during the coding time, many bugs came in when my module had to be integrated with other components of the project.

The week's works included:
  •  Add a code to the Jenkins integration test to change flag in the dirac.cfg in order to activate ElasticSearch backend for storing and accessing JobParameters. 
    • The code would be integrated into the Jenkins code for system testing. Uses CSAPI() of DIRAC service.
    • The commit can found here
  • Fix codes for generateFullIndexName() function error as it was moved into the class ElasticSearch to remove redundant imports to the same file.  Commit here.
    • Address the requested changes on the Pull request as asked by code owners and reviewers. Along with this, started and working with Jenkins testing service.
    • Brought efficiency to algorithms written earlier for fetching results with inputs from mentors.
    This was all done for this week and a Pull Request was made with respect to the same. Find the PR here. Tasks can be tracked for the next in the task manager (check sidebar).


    Comments

    Popular posts from this blog

    Week 10 :- CERN-HSF @ GSoC 2018

    This week, I started with the work that was optional and beyond the scope of the work as per the proposal. I started adapting the codes I modified or wrote for simultaneous support for Python2 and Python3. This needed first going through the guides which explain the porting process as well as following the guides as prescribed by the LHC project at CERN. I used the python-modernize library which supported this modification along with keeping the original support. Using this module, I modified most of the files involving ElasticSearch support as well as some of the codes I introduced/modified as part of the earlier works described in various posts of the blog. The series of commits can be found in Pull Request 3765 . Note: The work still needs to incorporate due to various other issues in automatic porting methods.

    Week 9 :- CERN-HSF @ GSoC 2018

    This week I was involved with working on Pull Request 3744  where some changes were demanded by other members of the organization as per the requirements of other components of the project. Firstly, as we moved towards adding a Jobs Status table (discussed in another post of the blog), which has eased and increased efficiency for query processing, we need to take care of the modules that accessed that table during any of there functions. Hence, it became important to analyze and test every module available in the Workload Management System as well as other modules that are accessing the table. A string of commits can be found below for the work done during this week: 0b1a63594eec932c12669d3274d5da705d9e2ffb fdda6f1fa473f866f0b552b838761f1201bc3c5b All the commits related to this issue can be found in this Pull Request .

    My GSoC experience with CERN-HSF, Summer 2018

    The Google Summer of Code (GSoC) program is one of the most prestigious programs for student developers, who are eager to work and demonstrate their skills in a full-fledged working environment. The program gives this opportunity to students all around the world and I feel good that I was selected for this program with the CERN-HSF organization, one of the pioneer organizations for nuclear research. My experience started before the GSoC program, with the first contact with the current mentor, Federico Stagni where we discussed the proposed project and my suitability for it by performing some tasks that are available here . Based on performance and my timelines, I submitted my proposal which went through multiple revisions with inputs from my mentor Federico and self-improvements. Finally, almost after a month of wait, students selected for GSoC 2018's program were announced and found myself fortunate to be selected with the following project with CERN-HSF:-  Monitoring and...