Some mahotas misc.

[Luis Pedro Coelho]

Hi list,

First of all some good news from me is that the mahotas paper got
"Accepted after minor revisions"!

I want to time version 1.0 to come out with the publication, but I'll
release a beta over the week-end (just need to clean up before the release).

*

In general, for some of the documentation, I have started using

import mahotas as mh


A bit of googling has told me some people like

import mahotas as mah
or
import mahotas as ma

However, I think it's best if there is some consistency and there seems
to be no general google consensus. Therefore, unless people here speak
up for "mah" (perhaps there is some conflict with another package), I am
going to start using "mh" throughout the docs (including in the new
draft of the publication, where I will add another worked out example).

Best,
Luis

[Thouis (Ray) Jones]

Congrats!

> --
> You received this message because you are subscribed to the Google Groups
> "pythonvision" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pythonvision...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Karol M. Langner]

Yeah, good job!

It's a shame it was a bit late for me to cite it in a recent article I publish. I did include a reference to the github repo, though:
http://onlinelibrary.wiley.com/doi/10.1002/adfm.201300091/references

I'll be sure to cite the paper in upcoming articles where I'm using the same scripts.

Cheers,
Karol

--
written by Karol M. Langner
Fri Apr 19 11:21:29 EDT 2013

[Luis Pedro Coelho]

On 04/19/2013 05:24 PM, Karol M. Langner wrote:
> Yeah, good job!
>
> It's a shame it was a bit late for me to cite it in a recent article I publish. I did include a reference to the github repo, though:
> http://onlinelibrary.wiley.com/doi/10.1002/adfm.201300091/references
>
> I'll be sure to cite the paper in upcoming articles where I'm using the same scripts.

Thanks.

I will cite you though as another example of someone using the library :)

In general, though, it's good to be able to get some credit for this
work. The code itself is useful for my research work, but it's citations
that pay for documentation and &c

Best,
Luis

[Karol M. Langner]

I definitely understand and will do so in the future. Couldn't get it in this time before the proof, though.

- Karol

--
written by Karol M. Langner

Mon Apr 22 14:48:36 EDT 2013

[Luis Pedro Coelho]

Karol (and everybody else):

The way I wrote my last post, it seemed like an accusation of you
personally, which was not my intention at all.

I was trying to make a general point about being happy that I can now
get some academic credit for a type of work which otherwise could be
seen as "slacking with a side project instead of doing research."

Unfortunately, I put it a context which made it into something non-intended.

I am sorry,
Luis

On 04/22/2013 08:49 PM, Karol M. Langner wrote:
> On Apr 22 2013, Luis Pedro Coelho wrote:
>> On 04/19/2013 05:24 PM, Karol M. Langner wrote:
>>> Yeah, good job!
>>>
>>> It's a shame it was a bit late for me to cite it in a recent article I publish. I did include a reference to the github repo, though:
>>> http://onlinelibrary.wiley.com/doi/10.1002/adfm.201300091/references
>>>
>>> I'll be sure to cite the paper in upcoming articles where I'm using the same scripts.
>>
>> Thanks.

>> po

[Karol M. Langner]

Luis,

It's OK. Even if you were mad at me I would understand :) I know how frustrating doing side projects and coding tools for your own research can be. Publishing as soon as possible definitely is helpful.

- Karol

--
written by Karol M. Langner

Mon Apr 22 16:37:28 EDT 2013