[L2Ork-dev] New developer interested in doing a GSOC18 project

[pranay gupta]

Hello Jonathan,

I have gone through all the mails and tried to go through some files also,
what I understood was that, wherever algorithms have been implemented using
single precision I have to change that to double precision and some
external libraries that are being called in the core functions might also
need changes. Also, support for backward compatibility, and an option to
the users whether to run purr date using single precision or double
precision should be added. And in case any of the single precision or
double precision catches an error, the one that works has to be used. Also,
you mentioned about single precision binaries performing better with better
algorithms as compared to double precision with a basic implementation when
compared to vanilla binaries as per the results of some tests.

I had a few doubts regarding the project,

1) What should be the main points that I should focus more on in my
proposal?

2) Also will any of the algorithms that are already implemented require any
implementation changes when adding support for double precision?

3) And it would be really helpful if you could provide me a few resources
that might make it easier for me to understand the project better?

Sincerely,
Pranay Gupta

On Thu, Mar 22, 2018 at 6:29 AM, Jonathan Wilkes <jon.w.wilkes at gmail.com>
wrote:

> On Wed, Mar 21, 2018 at 7:55 PM, Jonathan Wilkes <jon.w.wilkes at gmail.com>
> wrote:
> >> This is very much platform-dependent: platforms that do not have native
> support for 64bit floating point operations would surely suffer.
> >
>
> Also-- I think it would be quite workable to be able to specify at build
> time whether you want single or double-precision.
>
> Thinking about Albert's work on the build system lately, it should also
> be workable to simply exclude any library for either case that doesn't
> work correctly under that precision.
>
> -Jonathan
> _______________________________________________
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
> https://disis.music.vt.edu/listinfo/l2ork-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20180323/8a79be4a/attachment.html>