Re: [boost] GSoC Boost.Multiprecision project
Hello,
Hi Jyotesh.
Looking at the project description, I think I have understood what needs to be implemented in this project.
Yes, you seem to have a good grasp of the issues. Good work.
I have also gone through the current code cpp_bin_float.hpp and I have understood some part of it. I want to know how detailed should my proposal be? What details should I include in my proposal? What should be the deliverables for the project?
Go ahead and add some details from cpp_bin_float if you like. You can mention that this is a potential solution method.
Thank you for your valuable feedback. I have written project proposal for the first time in my life. So, I did not know what details to include. I have made some changes to my proposal as per your suggestions.
Other than that, I believe you have found the right level of detail, with a few more suggestions from my side below.
I have attached my proposal with this mail.
Please have a look at it and let me know your feedback. Thanks and regards,
I suggest you move the FFT algorithms to an optional part, add a bit more time for the elementary transcendental functions, and add some time for testing the various milestones in the project.
After that, you should start submitting your proposal. As far as I know, you can modify your proposal up to May 03.
I have written FFT algorithm as an optional algorithm now and made some changes to schedule. Please let me know if it is fine now.
Keep up the good work. Sincerely, Chris
I was studying the code for cpp_bin_float and I have some doubts in my mind.
1. What are eval_ops_signed_type, eval_ops_unsigned_type and
eval_ops_float_type?
2. What is the use of following lines?
typedef mpl::list
Hi Jyotesh.
Thank you for your valuable feedback. I have written project proposal for the first time in my life. So, I did not know what details to include. I have made some changes to my proposal as per your suggestions.
The proposal is a lot better. Now you need to submit it to Google's melange site. Please note that the proposal must be submitted to Googles melange site. Some candidates have been sending the proposals directly to us, and this is incomplete.
I was studying the code for cpp_bin_float and I have some doubts in my mind.
1. What are eval_ops_signed_type, eval_ops_unsigned_type and eval_ops_float_type?
Eval-ops are the global binary arithmetic operatory, and the eval_ops-types are those types that will be supported for global binary math with the radix-2 back-end.
2. What is the use of following lines? typedef mpl::list
signed_types; typedef mpl::list unsigned_types; typedef mpl::list float_types;
It's Boost's way of creating a list of built-in types. Again, these are the types that will be supported for global binary math.
These are not used in the class elsewhere. Similar lines are present in cpp_dec_float.hpp also and not used elsewhere in the class.
They are used by the multiprecision::number front-end to actually implement global binary math ops.
3. In the function from_float_type, I think the variable number_of_digits should be initialized to zero before using it in while loop.
cpp_bin_float is in a rudimentary state right now. It is not even close to working. That's the point of the GSoC project. So stuff might not be quite right yet.
Lastly, I have seen on mailing list, that some of the students are submitting code samples.
It's too late for code. Get your best shot at a good proposal onto melange. If you would like to submit code sample, you can do it after your proposal is up. Good luck. Sincerely, Chris. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
participants (2)
-
Christopher Kormanyos -
Jyotesh Choudhari