[yt-dev] Issue #1047: Radial Column Density (yt_analysis/yt)

[Matthew Turk]

Hi Bili,

I think it would be best to keep similar API structures -- that way we
can use HTM functionality elsewhere, too!

-Matt

On Sat, Jul 25, 2015 at 1:41 PM, Bili Dong <qobilidop at gmail.com> wrote:
> Hi Matt,
>
> Thanks for your suggestion. It’s a good idea to start with HTM and see how it works.
>
> I have a further question. From my observation, the healpix related functionality are mainly implemented in yt.utilities.lib.grid_traversal as several functions and in yt.visualization.volume_rendering.camera as several classes. When I’m implementing the HTM functionality, should I imitate that? Or should I start with implementing those methods locally within the radial_column_density submodule?
>
> -Bili
>
>> On Jul 24, 2015, at 12:54 PM, Matthew Turk <matthewturk at gmail.com> wrote:
>>
>> Hi Bili,
>>
>> I think it depends.  But, there are likely other ways to get this
>> functionality implemented; for now, even just using something like HTM
>> would work (even though it's not equal area) and then replace it later
>> once we have licensing figured out.
>>
>> -Matt
>>
>> On Thu, Jul 23, 2015 at 1:55 PM, Bili Dong <qobilidop at gmail.com> wrote:
>>> Another option I can think about is to reimplement the needed healpix
>>> functionality from scratch. Since only the coordinates transformation part
>>> are involved here, it would be some reasonable amount of work.
>>>
>>> But I’m not sure if only using the algorithm resolves the license problem,
>>> does it?
>>>
>>> -Bili
>>>
>>> On Jul 23, 2015, at 11:38 AM, Bili Dong <qobilidop at gmail.com> wrote:
>>>
>>> I see where the problem is. And since the whole HEALPix stuff is GPL. It’s
>>> even not possible to reimplement something like healpy, right?
>>>
>>> To keep the project in BSD,  I’m thinking about adding a parameter to the
>>> class RadialColumnDensity. By using that parameter,  the user can feed the
>>> healpix functionality to the class. Is that possible?
>>>
>>> -Bili
>>>
>>> On Jul 23, 2015, at 11:17 AM, Nathan Goldbaum <nathan12343 at gmail.com> wrote:
>>>
>>> Healpy is GPL, so that won't work.
>>>
>>> One way around this would be to implement the functionality you are
>>> concerned about in a new GPL package, split off from the main yt package.
>>>
>>> On Thursday, July 23, 2015, Bili Dong <qobilidop at gmail.com> wrote:
>>>>
>>>> Here’s the link to the issue. Sorry for not including it.
>>>>
>>>> Regards,
>>>> Bili
>>>>
>>>> On Jul 23, 2015, at 10:07 AM, Bili Dong <qobilidop at gmail.com> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> I’m bringing the update of the discussion here. The current problem is to
>>>> find a workaround for the code removed for licensing concerns. Could healpy
>>>> could be an option?
>>>>
>>>> Regards
>>>> Bili
>>>>
>>>>
>>> _______________________________________________
>>> yt-dev mailing list
>>> yt-dev at lists.spacepope.org
>>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> yt-dev mailing list
>>> yt-dev at lists.spacepope.org
>>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>>
>> _______________________________________________
>> yt-dev mailing list
>> yt-dev at lists.spacepope.org
>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
> _______________________________________________
> yt-dev mailing list
> yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org