User Details
- User Since
- Mar 5 2024, 3:51 AM (97 w, 4 d)
- Availability
- Available
- LDAP User
- AgarwalMahima
- MediaWiki User
- AgarwalMahima [ Global Accounts ]
Sat, Jan 10
Oct 10 2024
@Gopavasanth I have created a merge request for the above task : https://gitlab.wikimedia.org/toolforge-repos/yearinreview/-/merge_requests/7
Oct 3 2024
I have added an option for users to sort the tools based on tool title. This is something you were expecting, right?
https://github.com/gopavasanth/ToolWatch/pull/19
Aug 23 2024
The deployment of the tool on Toolforge is still in progress and, unfortunately, won't be completed today. Although today is officially the last day of my Outreachy internship, I want to let you know that I will continue volunteering until the final deployment is complete and the tool is fully ready for use, along with all the necessary documentation.
Aug 22 2024
Week 13: Aug 19 to Aug 23
Aug 20 2024
Week 12: Aug 12 to Aug 16
Aug 12 2024
Week 11: Aug 05 to Aug 09
Week 10: Jul 29 to Aug 02
Aug 5 2024
Frontend Prototype:
Jul 27 2024
Week 9: Jul 22 to July 26
Jul 19 2024
Week 8: Jul 15 to July 19
Week 7: Jul 08 to July 12
Jul 7 2024
Week 6: Jul 01 to July 07
Jul 1 2024
Week 5: June 24 - June 28
Jun 21 2024
Week 4: June 17 - June 21
Jun 16 2024
Week 3 : June 10 - June 14
Jun 9 2024
Week 2 : June 3 - June 7
May 29 2024
Week 1 : May 27 - May 31
May 23 2024
Apr 3 2024
Given that we can still edit the submitted notebook, would it be advisable to make further edits directly to it? Alternatively, if we intend to incorporate additional content beyond the original submission, should we create a new notebook for these purposes? Your guidance on the preferred approach would be appreciated.
Mar 31 2024
Mar 26 2024
Mar 25 2024
Mar 23 2024
@Ederporto, When can we expect to receive feedback on the public-paws-notebook submission?
Mar 21 2024
Mar 20 2024
Mar 19 2024
Mar 18 2024
Mar 17 2024
@Shruti799 , In order to get our notebook reviewed by the mentors , we have to mail it to them.
Mar 16 2024
Mar 15 2024
Mar 14 2024
@Ederporto Could you please provide a timeline of the work we plan to accomplish on the project, outlining the tasks we will complete at each step.
@Mitumoni_kalita
If displaying the graph is taking too much time, you can expedite the process by using a shorter dataframe. You can achieve this by utilizing the cum_sum_df.iloc[:,:20] slice, limiting the dataframe to the first 20 columns. This adjustment should streamline the graph generation process and allow for quicker visualization.
Simply save the video in a variable and return it.
Mar 13 2024
Mar 12 2024
Yes, if you use a try-catch block, your code won't halt upon encountering such errors; it will handle them and proceed to the next timestamp. Even if you receive the same traceback for multiple timestamps, the loop shouldn't terminate prematurely due to errors. By handling errors appropriately, the loop will continue execution, eventually retrieving data for some timestamps. From the screenshot you shared, it seems like your loop terminated at the first timestamp due to an unhandled error.
I suggest fetching data from the Wikimedia API by providing two consecutive revision timestamps: one as the start timestamp and the other as the end timestamp. Set the granularity to daily and check if data is available. You may not receive data for the first two timestamps, but you can attempt retrieval for subsequent timestamps.


















