Ed,
Frankly speaking I would even suggest rebasing + squashing the whole
longlong branch into one commit before merging to master (of course if
Chris agrees as most of the commits are from him). This will make it more
obvious that all these changes came together and make future investigation
None here, Ed. Thanks, Chris
On Mon, Aug 31, 2015 at 10:15 AM, Ed wrote:
> I’ll be pleased to write some tests for it that are basically what you
> have below. I’d also like to tidy up the lldf branch as it currently is by
> rebasing it to get rid of the merge commit.
>
> Chris, kmx, any object
The LongLong to Double conversion problems
appear to have been resolved. I would invite
any PDL developers with systems having lots
of RAM to test large memory operations.
We need to add some tests to check for correct
operation when the PDLs and index values are
>=2**31. For instance, here is
Hi Ingo,
I’ve pasted your 2.13 build file to this Github issue:
https://github.com/PDLPorters/pdla-core/issues/10
Best regards,
Ed
From: Ingo Schmid
Sent: Wednesday, August 26, 2015 9:02 AM
To: Zakariyya Mughal ; pdl-devel
Subject: Re: [Pdl-devel] Faster PDL Development Cycle---But How?
Hi,
Hi all: I would like to echo Craig's concern about keeping some
stability with at least one version of PDL.
Here at UCAR we have been using PDL almost since the project started.
We currently use PDL in production processing of GPS Radio Occultation
data that is used by all major world weather
I’ll be pleased to write some tests for it that are basically what you have
below. I’d also like to tidy up the lldf branch as it currently is by rebasing
it to get rid of the merge commit.
Chris, kmx, any objections?
Ed
From: Chris Marshall
Sent: Monday, August 31, 2015 10:58 AM
To: pdl-deve
The LongLong to Double conversion problems
appear to have been resolved. I would invite
any PDL developers with systems having lots
of RAM to test large memory operations.
We need to add some tests to check for correct
operation when the PDLs and index values are
>=2**31. For instance, here is
