|−|= Public application template = |+|
|−|This part is answered in public on your [[Special: MyPage|user page]]. Please copy its source ('''edit''') and then fill. Delete any examples and annotations (''this markup'') afterwards. Same for questions that do not apply to your situation. | |
| || |
|−|== A: An introduction == |+|
in ,one .
|−|* Please describe yourself in three sentences, one of them regarding your current studies. |+|
|−|** Which languages do you speak ? |+|
|−|** What's your overall background? ''The general field you work in or are studying, e. g. computer science, physics, artificial intelligence, control theory... '' |+|
.. . .
|−|* Why do you want to participate in the Google Summer of Code? What do you hope to gain by doing so ? |+|
|−|** Please also describe your previous experience with the GSoC, if any. ''Includes any community-bonding, mentor experience or application, not necessarily accepted. We use this subquestion to identify which students are unfamiliar with how the program goes, providing further support. It has no negative impact on your rating!'' |+|
to so . . to the
|−|* Why are you choosing Octave? |+|
| || |
|−|== C: Contact == |+|
|−|* Please state the (unique and identical where possible) nick you use on IRC and any other communication channel related to Octave. ''We really want unique nicks. You might want to bold it.'' |+|
in +. in . I to .to .
|−|* Which time zone do you live in ? Will that change over GSoC duration? ''Perhaps DST adjustment or a relocation. Note that both UTC and GMT are not aware of daylight saving time! Please state UTC+ x or -x. '' | |
|−|* Please state the timeframe (in UTC+0) when you feel most comfortable working during GSoC. Where are your time buffers? ''Example: I usually code around 9.00 to 18. 00 and could also try to start earlier (~7. 00) for few days ;-)'' | |
| || |
|−|== E: Coding experience == |+|
|−|This part is one of the more important ones in your application. You are allowed to be as verbose as you want, as long as you stay on topic ;-) |+|
,,. . experience with a what . and the .
|−|* Please describe your experience with C++, Octave or Matlab m-scripts, OpenGL and Qt. | |
|−|* Please describe your experience with other programming languages. | |
|−|* Please describe your experience with being in a development team. ''Do you have experience working with open source or free projects?'' | |
|−|* Please describe the biggest project you have written code for and what you learned by doing so. Also describe your role in that project over time. | |
|−|* Please state the commits and patches you already contributed to Octave. ''This question (one of the most important parts by the way) is the only part of your application our wiki admins will edit for you even after the application deadline. Code sometimes speaks louder than many words do. '' | |
| || |
|−|== F: Feeling fine == |+|
|−|* Please describe (in short) your experience with the following tools: ''We only use this question to determine where you need guidance, not for rating! We by no means expect you to be familiar with all of these and you'll won't necessarily need them while working with us. '' |+|
|−|** IRC and mailing lists |+|
|−|** Mercurial or other source code management systems | |
|−|** Mediawiki or other wiki software | |
|−|** make, gcc, gdb or other development tools | |
|−|* What will make you actively stay in our community after this GSoC is over? ''You can also tell us after applications close and we'll happily try to fulfill :-)'' | |
| || |
|−|== O: Only out of interest == |+|
|−|* Did you ever hear about Octave before? |+|
to be . to on
|−|** If so, when and where? How far have you been involved already? | |
|−|** If not, where would you expect or advise us to do advertising? | |
|−|* What was the first question concerning Octave you could not find an answer to rather quickly? ''Of course more than one question can be stated. We try to improve based on this each year! Includes learning how to use it, code, website, GSoC application, …'' | |
| || |
|−|== P: Prerequisites == |+|
|−|* Please state the operating system you work with. |+|
|−|** If you have access to more than one , please state them and the conditions under which you are granted this access. |+|
have one the which .() an
|−|* Please estimate an average time per day you will be able to ''( if separated) '' access |+|
a with the can .
|−|** an internet connection | |
|−|** a computer | |
|−|** a computer with your progressing work on | |
|−|* Please describe the degree up to which you can install new software on computers you have access to. | |
| || |
|−|== S: Self-assessment == |+|
|−|* Please describe how useful criticism looks from your point of view as committing student. |+|
|−|* How autonomous are you when developing? ''If you answer both subquestions with "Yes, definitely", we are a tad confused. ;-)'' | |
|−|** 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? | |
| || |
|−|== Y: Your task == |+|
and can . -
|−|* Did you select a task from our list of proposals and ideas? |+|
. '' ,, and of provide a for the . the and
|−|** 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 you apply for a task you have added yourself instead, please describe this task, its scope and people you already talked to concerning it. What field of tasks did you miss on the list? |+|
|−|* 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"). Optionally include two or three milestones you expect. '' |+|
like or (
1.) I am Sanpreet Singh. I am studying in Guru Nanak Dev Engineering College,Ludhiana pursuing my degree in electronics and communication. I belief in one thing that Nobody is perfect and I am nobody.
2.) I speak English,Punjabi and Hindi.
3.) I Am a electronics and communication engineer.
4.) I am lover of removing bugs. The approach of me is to serve humanity and removing bugs is also a way to serve humanity. I will gain confidence in life that I am capable of solving problems in life and sharing knowledge accross the world.
5.) I am participating in Gsoc for the first time.
6.) The answer is very logical. Octave is a software to implement Digital signal processing.I am a electronics engineer so I need to implement programming of DSP in some software. Previously I used matlab. But when I shifted to open source I found Open source more helpful. Secondly the project that I choose is of my interest.
2.) My nickname on irc is Sanpreet.
3.) My Time Zone is Asia/kolkata. I am living in india and my time is 9:30 hours ahead than US. My UTC is UTC+5:30 P.M
I have experience in programming in c++. Digital Signal Processing was our subject in 6th Semester in which programming in which I did programming in matlab . From January I have shifted to opensource and I started using open source and I have worked on live project using open source.In my project I have used perl language to draw dynamic graphs using gnuplot.
I was using matlab but when I started shifting I learned about kicad ,gnuplot,octave. Open source does not need any advertisement. The first experience with octave is when I created a account on wiki,Then a simple question was asked to me what is octave output of round(sinh(9)). So I installed octave and got the answer.
2.) I can give 15hours per day. I like to
I didnot believe in Autonomous nature. I want to be open. I donot wait for anybody to give me work. Coding is my hobby and I will work on them all throughout the life.
2.) I have selected the one idea. I liked fixing the audio processing in octave.Fix audio processing in octave: Audio processing is currently almost completely broken in Octave. Fix means there is a problem which has to be solved. Audio processing only works with linux open sound system.The Open Sound System (OSS) is an interface for making and capturing sound in Unix and Unix-like operating systems. Suggestion is make this
a part of audio package but the problem is whether the core functions are lacking presently or not .If Yes then core function like play and record has to be created. Like stated above audio processing works only with LOSS(Linux open sound system). Playing and recording is done in ubuntu with the help of libraries like Portaudio and classes like rtaudio. But this libraries are not working in other operating system. Either the core functions in other operating system other than linux cannot use the above libaries and I am confident that I can fix this.
Next objective is implementing audiorecorder and audioplayer classes.I will make core function which will be platform independent which can use the above libraries. PortAudio is a free, cross-platform, open-source,
audio I/O library. It lets you write simple audio programs in 'C' or C++ that will compile and run on many platforms including Windows,Macintosh OS X, and Unix (OSS/ALSA) and RtAudio is a set of C++ classes that provide a common API (Application Programming Interface)for realtime audio input/output across Linux, Macintosh OS-X and Windows operating systems. So I can make the core function but I need time to make it. I have installed XchartIRC and I have given the nickname and there we can share ideas.
I will study Where is problem. Whether function like play or record cannot call libraries(portaudio) in all the operating system.
The problem found above will be implemented.
Will do the implementation of libraries on every operating system.
Will make Some more cross independent functions that can also use the open source libraries to do some more attractive functions in octave. This I have not decided yet but I will do in this date.
I will implement all what I stated above upto international level.
Start documentation (using LaTeX or any other tool recommended) including developers documentation, user’s documentation (including MAN pages of command).