<div dir="ltr">Iain Duff gave us the permission to distribute MC64 in SuperLU_DIST. SuperLU Users' Guide (Page 14-15) mentioned 3 Copyright notices in the entire packages. The one from Xerox (did with John Gilbert) does not have any restriction. MC64 is mostly free, but with the following restriction<div>
<br><div>"The user shall not pass this code directly to a third party without the </div><div>express prior consent of the authors. Users wanting to licence their </div><div>own copy of these routines should send email to <a href="mailto:hsl@aeat.co.uk">hsl@aeat.co.uk</a> "</div>
<div><br></div></div><div style>In fact, if the user asks HSL, they will get the newer version: HSL_MC64:</div><div style><a href="http://www.hsl.rl.ac.uk/catalogue/hsl_mc64.xml">http://www.hsl.rl.ac.uk/catalogue/hsl_mc64.xml</a><br>
</div><div style>Since I don't need the new function, I didn't ask for update.</div><div style><br></div><div style>I can see the following types of usages:</div><div style><br></div><div style>1) The users use SuperLU_DIST, and package it in their products. This is probably ok.</div>
<div style>2) The users download SuperLU_DIST, but only extract MC64 for the other purposes. I think there is problem. </div><div style><br></div><div style>In any case, it's hard to control. I did get a couple of commercial users, they asked about not to use MC64 to avoid License issue. I suggest them to comment out the "row permutation" code (pivoting), and remove MC64. Their linear systems seem okay without MC64, and that's the option they chose.</div>
<div style><br></div><div style>Sherry</div><div style><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Nov 20, 2013 at 2:52 PM, Barry Smith <span dir="ltr"><<a href="mailto:bsmith@mcs.anl.gov" target="_blank">bsmith@mcs.anl.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Rob,<br>
<br>
Thanks.<br>
<br>
But since SuperLU_dist is freely distributed doesn’t this mean one could always just get SuperLU_Dist whenever they wanted to use MC64AD? Note the SuperLU_Dist license<br>
<a href="http://crd-legacy.lbl.gov/~xiaoye/SuperLU/License.txt" target="_blank">http://crd-legacy.lbl.gov/~xiaoye/SuperLU/License.txt</a> states that SuperLU_Dist can be included in other software including binary form but presumably this does not apply to MC64AD.<br>
<br>
Sherri,<br>
<br>
When your commercial buddies put SuperLU_Dist into some product do they also get permission from Iain to include MC64AD?<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
Barry<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Nov 20, 2013, at 4:36 PM, Falgout, Rob <<a href="mailto:falgout2@llnl.gov">falgout2@llnl.gov</a>> wrote:<br>
<br>
> Hi Barry,<br>
><br>
> We've already asked Sherri about this, and she says she has permission to use it in DSuperLU. It's in hypre because we currently bundle DSuperLU in our release.<br>
><br>
> -Rob<br>
><br>
>> -----Original Message-----<br>
>> From: Barry Smith [mailto:<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>]<br>
>> Sent: Wednesday, November 20, 2013 2:23 PM<br>
>> To: Falgout, Rob; Xiaoye S. Li<br>
>> Cc: petsc-dev<br>
>> Subject:<br>
>><br>
>><br>
>> Sherri and Rob,<br>
>><br>
>> I noticed both of you guys distribute MC64AD with your libraries which<br>
>> includes the following copyright/license statement. Did you receive permission<br>
>> to distribute this source code from Iain or Jacko and how general is that<br>
>> permission, just for you or for other groups also? That is, is there an alternative<br>
>> license that allows this source code to be distributed?<br>
>><br>
>> Thanks<br>
>><br>
>> Barry<br>
>><br>
>><br>
>><br>
>> CCCCC COPYRIGHT (c) 1999 Council for the Central Laboratory of the<br>
>> CCCCC Research Councils. All rights reserved.<br>
>> CCCCC PACKAGE MC64A/AD<br>
>> CCCCC AUTHORS Iain Duff (<a href="mailto:i.duff@rl.ac.uk">i.duff@rl.ac.uk</a>) and Jacko Koster (<a href="mailto:jak@ii.uib.no">jak@ii.uib.no</a>)<br>
>> CCCCC LAST UPDATE 20/09/99 CCCCC C *** Conditions on external use *** C C<br>
>> The user shall acknowledge the contribution of this C package in any publication<br>
>> of material dependent upon the use of C the package. The user shall use<br>
>> reasonable endeavours to notify C the authors of the package of this<br>
>> publication.<br>
>> C<br>
>> C The user can modify this code but, at no time C shall the right or title to all or<br>
>> any part of this package pass C to the user. The user shall make available free of<br>
>> charge C to the authors for any purpose all information relating to any C<br>
>> alteration or addition made to this package for the purposes of C extending the<br>
>> capabilities or enhancing the performance of this C package.<br>
>> C<br>
>> C The user shall not pass this code directly to a third party without the C express<br>
>> prior consent of the authors. Users wanting to licence their C own copy of these<br>
>> routines should send email to <a href="mailto:hsl@aeat.co.uk">hsl@aeat.co.uk</a> C C None of the comments from<br>
>> the Copyright notice up to and including this C one shall be removed or altered in<br>
>> any way.<br>
>><br>
><br>
<br>
</div></div></blockquote></div><br></div>