Editing User:Sudhir27
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 45: | Line 45: | ||
*:Fixed some part of the bug #51333 [https://github.com/Alok009/Octave/blob/master/dot.m] and currently working on it to implement all those matrices functions | *:Fixed some part of the bug #51333 [https://github.com/Alok009/Octave/blob/master/dot.m] and currently working on it to implement all those matrices functions | ||
*:Provided the code for the missing function 'rms' from signal package [https://github.com/Alok009/Octave/blob/master/rms.m]. | *:Provided the code for the missing function 'rms' from signal package [https://github.com/Alok009/Octave/blob/master/rms.m]. | ||
== F: Feeling fine == | == F: Feeling fine == | ||
Line 86: | Line 85: | ||
== S: Self-assessment == | == S: Self-assessment == | ||
* Please describe how useful criticism looks from your point of view as committing student. | * Please describe how useful criticism looks from your point of view as committing student. | ||
* How autonomous are you when developing: | * How autonomous are you when developing: | ||
** Do you like to discuss changes intensively and not start coding until you know what you want to do? | ** Do you like to discuss changes intensively and not start coding until you know what you want to do? | ||
** Do you like to code a proof of concept to 'see how it turns out', modifying that and taking the risk of having work thrown away if it doesn't match what the project or original proponent had in mind? | ** Do you like to code a proof of concept to 'see how it turns out', modifying that and taking the risk of having work thrown away if it doesn't match what the project or original proponent had in mind? | ||
== Y: Your task == | == Y: Your task == | ||
* Did you select a task from our list of proposals and ideas? | * Did you select a task from our list of proposals and ideas? | ||
** If yes, what task did you choose? Please describe what part of it you especially want to focus on if you can already provide this information. ''Please also wiki-link the page for your elaborated proposal here.'' | ** If yes, what task did you choose? Please describe what part of it you especially want to focus on if you can already provide this information. ''Please also wiki-link the page for your elaborated proposal here.'' | ||
* Please provide a rough estimated timeline for your work on the task. ''This should include the GSoC midterms and personal commitments like exams or vacation ("non-coding time"). If possible, include two or three milestones you expect.'' | * Please provide a rough estimated timeline for your work on the task. ''This should include the GSoC midterms and personal commitments like exams or vacation ("non-coding time"). If possible, include two or three milestones you expect.'' | ||
[[Category: Summer of Code]] | |||
[ | ------------------------------------------------------------------------------------ | ||
PolarAxes and Plotting Improvements[edit] | |||
Octave currently provides supports for polar axes by using a Cartesian 2-D axes and adding a significant number of properties and callback listerners to get things to work. What is needed is a first class implementation of a "polaraxes" object in C++. This will require creating a new fundamental graphics object type, and programming in C++/OpenGL to render the object. When "polaraxes" exist as an object type then m-files will be written to access them including polaraxes.m, polarplot.m, rticks.m, rticklabels.m, thetaticks, thetaticklabels.m, rlim.m, thetalim.m | |||
Minimum requirements | |||
Ability to read and write C++ code. Ability to read and write Octave code. Experience with OpenGL programming is optional. | |||
Difficulty | |||
Medium. | |||
Mentor | |||
Rik |