45
edits
Nvs-abhilash (talk | contribs) |
Nvs-abhilash (talk | contribs) |
||
Line 141: | Line 141: | ||
*::# Continuously interact with the mentors and better define the steps to complete the project. | *::# Continuously interact with the mentors and better define the steps to complete the project. | ||
*: '''May 30 - June 30, 2017''' (First term) | *: '''May 30 - June 30, 2017''' (First term) | ||
*:: | *:: '''Week 1-2''': Improve Pytave code | ||
*:: | *::# Migrate away from Pytave legacy [https://bitbucket.org/mtmiller/pytave/issues/74/migrate-away-from-remaining-pytave-legacy #74] [https://bitbucket.org/mtmiller/pytave/issues/80/remove-code-for-calling-octave-from-python #80] | ||
*:: | *::# Resolve [https://bitbucket.org/mtmiller/pytave/issues/79/sympy-function-objects-cause-errors #79], this causes test failures in Octsympy. | ||
*:: | *::# Remove the boost dependencies from Pytave and use native API calls for the same. | ||
*:: | *:: '''Week 3-4''': Making @sym a subclass of @pyobject. | ||
*::# | *::# Fix core Octave classdef issues: | ||
*:: | *::#: Understand the currently available features of classdef in Octave. | ||
*:: | *::#: Fix the bugs related to classdef in core Octave. Some of the major ones that I want to focus on are: | ||
*:: | *::#:* [https://savannah.gnu.org/bugs/?49169 49169] Defining a classdef superiorto some other classdef. | ||
*:: | *::#:* [https://savannah.gnu.org/bugs/?45833 45833] support load/save of classdef objects. | ||
*:: | *::#:* [https://savannah.gnu.org/bugs/?48693 48693] classdef subsref method is not called with correct nargout value. | ||
*:: | *::#:* [https://savannah.gnu.org/bugs/?43047 43047] and [https://savannah.gnu.org/bugs/?49169 49169] Documentation problems in classdef (Optional) | ||
*:: | *::#: Add more features if feasible. | ||
*:: | *::# Make this [https://github.com/cbm755/octsympy/pull/590 PR] by Abhinav mergeable. (If possible in the time frame) | ||
*:: | *::# Discuss and decide which implementation (classic @class style or classdef) style to use for the project. | ||
*: '''July 1 - July 24, 2017''' (Second term) | *: '''July 1 - July 24, 2017''' (Second term) | ||
*::# Make @sym instance a @pyobject instance by calling the constructors, and fixing tests and bugs. | *::# Make @sym instance a @pyobject instance by calling the constructors, and fixing tests and bugs. | ||
Line 165: | Line 165: | ||
*::# Write / Modify tests for the above changes. | *::# Write / Modify tests for the above changes. | ||
*: '''July 28 - August 21, 2017''' (Final term) | *: '''July 28 - August 21, 2017''' (Final term) | ||
*:: '''Week 9-10''': Write Documentation | |||
*::# Complete any pending tasks (if any). | *::# Complete any pending tasks (if any). | ||
*::# Write | *::# Write documentation for Pytave both user's guide and developer's guide. (This will help in attracting more developers to use Pytave) | ||
*::# | *::# Write extensive documentation for Octsympy. | ||
*::# | *::# Write documentation for the current implementation of classdef in Octave. (I think this is not completed yet.) | ||
*:: '''Week 10-12''': Fix further issues | |||
*::# Fix issues in Pytave [https://bitbucket.org/mtmiller/pytave/issues?status=new&status=open issue list]. | |||
*::# Fix issues in Octsympy [https://github.com/cbm755/octsympy/issues issue list]. | |||
*::# Add missing functions and functionality to Octsympy. | *::# Add missing functions and functionality to Octsympy. | ||
*: This is a very rough timeline. The exact steps will become clearer when I do some more discussion with the mentors. | *: This is a very rough timeline. The exact steps will become clearer when I do some more discussion with the mentors. | ||
[[Category: Summer of Code]] | [[Category: Summer of Code]] |
edits