Hey Namik,
Congratulations! :-)
Yes, we very hope that you'll stay with us in this adventure. I personally
really like open-source development because (1) it's really educative, and
(2) it makes me feel free. I think that research/jobs can put a lot of
pressure on me, to the point that it can become somewhat alienating. Having
a time window to develop my personal projects somehow keeps me optimistic :p
Open-Source software is actually not only about coding. I think you could
further improve your GUI by clearly defining when it should be used, and
when it shouldn't. Assume that your GUI ends up being (mis?)used by some
technical journalists, how would you like them to comment the results? If
you don't tell them the limits of your GUI, they can't know! If you want my
idea on the topic:
-> The GUI will indicate the performance of an "average program" (not tuned
for any particular architecture) on different devices. This can reveal some
information such as "It's hard to optimize code for this device, but if you
do this maybe you'll get some amazing results ; I don't know".
-> The GUI *does not* compare the peak performance of two different
devices. Whoever uses the GUI has to be extremely careful about it. This is
exactly what NVidia/AMD/Intel/WhicheverVendor is doing when presenting an
eyecandy slide that says : "oh, look how better our GPU is for Numerical
Computing". A lot of researchers/journalists fall into this trap, and this
is pretty sad.
I guess that these two examples give you a clear direction in which you
could document your code. Don't hesitate to add a "usage" section in the
GUI, to give some guidelines on how the results should be interpreted.
Philippe
2014-08-25 20:21 GMT+02:00 Namik Karovic <namik.karo...@gmail.com>:
> Hi Karl,
>
>
> thanks, Namik! Congratulations on successfully completing the GSoC
>> project. I hope you got a good insight in how open source projects are done
>> and how much fun it could be (although at some point one also needs to make
>> sure 'things get done' by dealing with not-so-much fun stuff).
>
>
> Thanks. I must say it felt damn good to finally work on something that's
> big and important :)
>
>
> The important next step is to finalize the first release. I don't think
>> there's much left to be done feature-wise, now it's mostly a matter of
>> cleaning up and packaging. We hope to have you with us not only for this
>> step, but also for the later future. The central idea of GSoC is to grow
>> the community of open source projects, so we're hoping and encourage you to
>> stay with us to the extent possible considering your other constraints such
>> as course work.
>
>
> How long I'll stick around depends on how much free time I'll have. I'm
> currently looking for a job, and if I manage to find one, I'm afraid I
> won't have a lot of free time.
>
>
> In your case the documentation part wasn't that urgent, because the GUI is
>> mainly a matter of fusing available functionality from ViennaCL together.
>> The two 'TODOs' with respect to documentation are:
>> - Document the source code using Doxygen-style comments, just like in
>> the ViennaCL source tree. Ideally, this is done right when writing code,
>> because then any assumptions on function arguments are clear.
>> - Write a user manual on how the GUI works (including some screenshots,
>> etc.). This last part, however, should be written right before the release
>> in order make sure that the screen shots are up-to-date.
>
>
> Alright, I'll get down to writing documentation now.
>
> Regards, Namik
>
>
> On Mon, Aug 25, 2014 at 1:33 PM, Karl Rupp <r...@iue.tuwien.ac.at> wrote:
>
>> Hi Namik,
>>
>>
>> > I'd like to send a big thanks to Karl and Philippe for the positive GSoC
>>
>>> final evaluation mark.
>>> And a big thanks to everyone for helping me with my project.
>>> Also, congrats to Toby for successfully completing his GSoC project.
>>>
>>
>> thanks, Namik! Congratulations on successfully completing the GSoC
>> project. I hope you got a good insight in how open source projects are done
>> and how much fun it could be (although at some point one also needs to make
>> sure 'things get done' by dealing with not-so-much fun stuff).
>>
>>
>>
>> It's been a great experience and a pleasure to work with you guys. I
>>> plan to continue working on the Benchmark GUI, at least until it's in a
>>> respectable shape. I'd also like to offer my help if you plan on making
>>> the benchmark result website a reality. Of course, I won't be as active
>>> as I was during GSoC.
>>>
>>
>> The important next step is to finalize the first release. I don't think
>> there's much left to be done feature-wise, now it's mostly a matter of
>> cleaning up and packaging. We hope to have you with us not only for this
>> step, but also for the later future. The central idea of GSoC is to grow
>> the community of open source projects, so we're hoping and encourage you to
>> stay with us to the extent possible considering your other constraints such
>> as course work.
>>
>>
>>
>> Also, there's one thing still unclear to me. What about documentation?
>>> Was I supposed to have written it by now? Or was the plan to start
>>> writing it after the final evaluations, and upload it to Melange
>>> together with my code sample once it's done? And in what format/style
>>> should the documentation be written?
>>>
>>
>> In your case the documentation part wasn't that urgent, because the GUI
>> is mainly a matter of fusing available functionality from ViennaCL
>> together. The two 'TODOs' with respect to documentation are:
>>
>> - Document the source code using Doxygen-style comments, just like in
>> the ViennaCL source tree. Ideally, this is done right when writing code,
>> because then any assumptions on function arguments are clear.
>>
>> - Write a user manual on how the GUI works (including some screenshots,
>> etc.). This last part, however, should be written right before the release
>> in order make sure that the screen shots are up-to-date.
>>
>> Best regards,
>> Karli
>>
>>
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds. Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> ViennaCL-devel mailing list
> ViennaCL-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/viennacl-devel
>
>
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
ViennaCL-devel mailing list
ViennaCL-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/viennacl-devel
