Re: [julia-users] Can't use

[Ivan Ogasawara]

Maybe I did not understand your question, but using DataFrames, I have this:

head(dv::AbstractDataArray{T,1}) at
/home/user/.julia/v0.3/DataArrays/src/datavector.jl:1
head(df::AbstractDataFrame,r::Int64) at
/home/user/.julia/v0.3/DataFrames/src/abstractdataframe/abstractdataframe.jl:141
head(df::AbstractDataFrame) at
/home/user/.julia/v0.3/DataFrames/src/abstractdataframe/abstractdataframe.jl:142


2015-04-15 10:12 GMT-03:00 Marcus Appelros :

> What is the output of methods(head)?

Re: [julia-users] Julia gets a mention in phys.org

[Ivan Ogasawara]

very interesting!

2015-04-13 13:30 GMT-03:00 René Donner :

> You can find more information on Picture here:
> http://mrkulk.github.io/www_cvpr15/
>
> Am 13.04.2015 um 18:24 schrieb Seth :
>
> > http://phys.org/news/2015-04-probabilistic-lines-code-thousands.html
> >
> > Joining Kulkarni on the paper are his adviser, professor of brain and
> cognitive sciences Josh Tenenbaum; Vikash Mansinghka, a research scientist
> in MIT's Department of Brain and Cognitive Sciences; and Pushmeet Kohli of
> Microsoft Research Cambridge. For their experiments, they created a
> probabilistic programming language they call Picture, which is an extension
> of Julia, another language developed at MIT.
> >
>
>

Re: [julia-users] Re: movingpastasquishedcaseconvention?

[Ivan Ogasawara]

I prefer underscore, because it is the same used for constant's name.

2015-02-06 7:26 GMT-02:00 Steven Sagaert :

> I prefer Java's camelcase: searchSortedLast: it's the same length as all
> lower case but clearer.
>
>
> On Thursday, February 5, 2015 at 8:12:43 PM UTC+1, David James wrote:
>>
>> Hello,
>>
>> The title of this post is "Moving Past a Squished Case Convention" not
>> "Moving Pastas Quiche...". :)
>>
>> The Julia standard library tends to use the "squishedcase" notation.
>> Being concise is great for mathematical functions, like sin, cos, and ln.
>> However, it is cognitively harder for people for "compound" function names;
>> e.g. "searchsortedlast". Such a naming convention flies in the face of real
>> programming experience. It makes programming harder for people.
>>
>> There are many sane ways to name functions. Lisps tend to use hyphens,
>> others often use underscores. R libraries use a non-standard mix [1].
>> Interestingly, the Julia parser code itself uses hyphens; e.g.
>> prec-assignment and prec-conditional: https://github.com/JuliaLang/
>> julia/blob/master/src/julia-parser.scm
>>
>> It would be a shame for squishedcase to persist as the language reaches
>> 1.0. What are some possible ways to address this problem without breaking
>> compatibility in the short-run?
>>
>> I see a possible solution. Choose a character and encourage its use to
>> break apart words; e.g. -, _, or a middot (·) [2]. Make it highly
>> recommended but non-breaking until 1.0. Deprecate
>> functionsusingsquishedcase.
>>
>> Julia is great overall but lacking in this way. Let's make it better.
>>
>> Sincerely,
>> David
>>
>> [1] http://stackoverflow.com/questions/1944910/what-is-
>> your-preferred-style-for-naming-variables-in-r
>>
>> [2] The middot is relatively unobtrusive and doesn't take up much space
>> horizontally, e.g. search·sorted·last. It is also useful for variables
>> representing compound units; e.g. N·m.
>>
>>
>>
>>

Re: [julia-users] ANN: Docile & Lexicon update.

[Ivan Ogasawara]

great!
El 21/01/2015 14:22, "Michael Hatherly" 
escribió:

> Hi all,
>
> I’m pleased to announce the latest update to the Docile
>  and Lexicon
>  documentation packages.
>
> New features include:
>
>- Docile now supports plain strings
>,
>ie. without @doc, as docstrings. Compatibility with the Julia 0.4 doc
>system is still present.
>- Thanks to Tom Short, Lexicon can now output nicely formatted
>markdown. This can then be used to create static documentation using
>programs such as MkDocs . See the
>documentation from the following packages for examples of the results:
>Sims , Docile
>, and Lexicon
>.
>
> Any bugs or feature requests can be opened in either the Docile or Lexicon
> repos.
>
> Happy documenting!
>
> — Mike
> ​
>

Re: [julia-users] Re: switch case statement?

[Ivan Ogasawara]

very interesting!
El 18/01/2015 15:50, "Ismael VC"  escribió:

> There is also a Switch package for Julia:
> https://github.com/dcjones/Switch.jl
>
> El domingo, 16 de diciembre de 2012, 5:00:17 (UTC-6), Erik Engheim
> escribió:
>>
>> I can not seem to find any type of *switch case* statement in Julia.
>> What is the alternative? I know I could always use *elseif *but that is
>> cumbersome. My thinking was that perhaps due to the type system one does
>> not need switch case as often. Usually we use swith case with enums, but I
>> guess in Julia one could use types, and just define a bunch of short
>> functions. But this is just speculation on my side I would have loved to
>> hear what the thinking is behind leaving out *switch-case* functionality.
>
>

Re: [julia-users] Foro julia-user-es, para discutir acerca de Julia en español.

[Ivan Ogasawara]

Genial :)
El 14/01/2015 17:59, "Ismael VC"  escribió:

> Foro julia-user-es, para discutir acerca de Julia en español: :D
>
> https://groups.google.com/forum/#!forum/julia-users-es
>

Re: [julia-users] Re: Later methods definition replaces the previous one?

[Ivan Ogasawara]

Hi, I am newbie yet, but maybe julia could have an operator to wrap a
function call to specific type from specific module:

## module file

module modA

  export TypeC, setx

  type TypeC

x

  end

  function setx(c::TypeC, v::Any)

c.x = v

  end

end

## other file

and on other file maybe we can call the setx like: objC.setx(v) and this
would be a wrap to setx(objC, v). I know we can define a function into the
type ... but this probably will down the performance and will go to
different way for the multiple dispatch.

PS:: again, sorry i'm a newbie julian :)


Ivan Ogasawara


El 13/01/2015 19:45, "Mauro"  escribió:

> > I would argue that this would be prohibited by the compiler as it could
> not
> > distinguish between
> >  foo(x::Number) = 2
> > and
> > foo(x::Float64) = 3
>
> Yes it can:
>
> julia> foo(x::Number)=1
> foo (generic function with 1 method)
>
> julia> foo(x::Float64)=2
> foo (generic function with 2 methods)
>
> julia> foo(5)
> 1
>
> julia> foo(5.)
> 2
>
> > In the example I gave, count was allowed to be exported from my two
> modules
> > just by being defined by Base. Yet the two count's have different
> meanings
> > from each other and from the Base.count. On the other hand steadystate()
> > was not merged even though the end-result is the SAME: one would have two
> > methods that work on different types of arguments and do different
> things.
>
> I don't think it is good practice to add unrelated methods to generic
> functions in Base.  A guide-line could be to check whether your methods
> matches up with the help text, if so, add it to Base.count otherwise
> not.  If not, either give it a different name or do not export it, so
> the user has to fully qualify it MyMod.count.
>
> This is just my opinion but I suspect at least some share it.
>

Re: [julia-users] Re: Julia documentation is ready for translation/internationalization on Transifex!

[Ivan Ogasawara]

***2 years ago

2014-12-28 14:26 GMT-02:00, Ivan Ogasawara :
> I saw apertium 5 years ago on FISL (Brazil) ... It seems great... but i've
> never work with that ... this can be the first time :)
>
> 2014-12-28 13:41 GMT-02:00 SVAKSHA :
>
>> On Fri, Dec 26, 2014 at 9:15 PM, Ismael VC 
>> wrote:
>> >
>> > My ulitmate goal is that once most of the strings are translated and
>> > reviewed, make a program automatically update the resources, when the
>> > tracked files are changed and get a notification, if I can get some
>> people
>>
>> Would Apertium[1] help you automate the Spanish translation process?
>> IIRC, they support En<->Es and the rate was quite good -  iirc, was
>> above 70% (sorry, its been many years so I'm not sure if that has
>> changed, which I'm sure it has since they have been a regular
>> participant in GSOC and the engine must have improved in leaps over
>> the years).
>>
>> Ofcourse, you would still need to manually verify the strings but it
>> helps you automate most of the regular stuff you could perhaps train
>> it for any terms that are missing.
>>
>> Francis is one of the lead devs among others and they are a helpful
>> bunch - if you prefer irc, hop over to #apertium on freenode.
>>
>> [1] https://en.wikipedia.org/wiki/Apertium
>> HTH,
>> -SVAKSHA ॥  http://about.me/svaksha  ॥
>>
>

Re: [julia-users] Re: Julia documentation is ready for translation/internationalization on Transifex!

[Ivan Ogasawara]

I saw apertium 5 years ago on FISL (Brazil) ... It seems great... but i've
never work with that ... this can be the first time :)

2014-12-28 13:41 GMT-02:00 SVAKSHA :

> On Fri, Dec 26, 2014 at 9:15 PM, Ismael VC 
> wrote:
> >
> > My ulitmate goal is that once most of the strings are translated and
> > reviewed, make a program automatically update the resources, when the
> > tracked files are changed and get a notification, if I can get some
> people
>
> Would Apertium[1] help you automate the Spanish translation process?
> IIRC, they support En<->Es and the rate was quite good -  iirc, was
> above 70% (sorry, its been many years so I'm not sure if that has
> changed, which I'm sure it has since they have been a regular
> participant in GSOC and the engine must have improved in leaps over
> the years).
>
> Ofcourse, you would still need to manually verify the strings but it
> helps you automate most of the regular stuff you could perhaps train
> it for any terms that are missing.
>
> Francis is one of the lead devs among others and they are a helpful
> bunch - if you prefer irc, hop over to #apertium on freenode.
>
> [1] https://en.wikipedia.org/wiki/Apertium
> HTH,
> -SVAKSHA ॥  http://about.me/svaksha  ॥
>

Re: [julia-users] Re: Julia documentation is ready for translation/internationalization on Transifex!

[Ivan Ogasawara]

Hi Ismael, maybe I can help you with Brazilian Portuguese and Spanish
translations.

this week I'm on vacation .. but the next week I can start it (maybe 2
hours per week).

I need to learn too the transifex editor .. but I think it not will be a
problem :)

Translation Memory will be great ... but the only one I know is
http://anaphraseus.sourceforge.net/ to openoffice :(

Probably I will need a help to start the project :)

My best regards

2014-12-26 19:15 GMT-02:00 Ismael VC :

> Well I was told that historicaly people were encouraged not to spend too
> much energy translating the docs because they are not static (and I see
> that still hasn't changed). I thought there wasn't much interest, so I left
> the idea for a while and stoped looking for advance in this field.
>
> But I've been planing this for a while, after all I want to be a
> programmer, and learn how to automate this kind of stuff the most I can and
> solve problems, etc (I don't mind about non-staticness, as a matter of fact
> I like the idea of keep on learning Julia at the same time I do this):
>
>- How to translate the docs: http://bit.ly/13Kgt18
>- Does anyone has any experience in computer aided translating?:
>http://bit.ly/144ZIyy
>- Advice about git repository layout: http://bit.ly/1zncd0b
>
>
> I'm just so tired of JIT translating from the manual when I'm in the
> classroom or when explaining what Julia is and why it is important to learn
> and use, to someone, over and over again, I think I can get a group of
> students from my school to aid me in the review process, I've talked to one
> of my profesors about giving them some extra credits or something.
>
> Waldir I would love to get feedback from you, I just followed the sphinx
> instructions, but if there are better options that benefit all the non
> english people, I would like to implement them as soon as posible (while my
> vacations last), this would be the best time to do this since the project
> is just starting, but either way I'm not stoping this time, I just want to
> get it done and done well.
>
> My ulitmate goal is that once most of the strings are translated and
> reviewed, make a program automatically update the resources, when the
> tracked files are changed and get a notification, if I can get some people
> to translate or review in trasifex (even if it is just one string a day, 5
> minutes of their time) from their cellphones instead of watching them waste
> all day playing candycrush or whatever (most of the smarphone people I know
> do this), then that would make me very very happy.
>
> I absoulutely want this manual on my school library!
>
> El viernes, 26 de diciembre de 2014 11:27:38 UTC-6, Waldir Pimenta
> escribió:
>
>> Hi Ismael,
>>
>> First of all, thanks for doing this :)
>>
>> I am not sure if you announced your plans to work on this in advance, so
>> sorry if I missed it and thus the opportunity to provide early feedback.
>> The last time I saw the issue of translating the documentation using a
>> translation platform being discussed, I mentioned my concerns about the
>> choice of platform
>> ,
>> particularly regarding two features I consider extremely useful:
>> translation memory / machine translation (which ends up saving a lot of
>> typing, as well as ensuring consistency), and the ability for users to
>> choose their language fallback chain (e.g. a Portuguese user could pick
>> Brazilian Portuguese, Galician, and Spanish as fallback languages), which
>> again allows a much more efficient translation workflow and often help
>> escaping ambiguity holes due to insufficient context.
>>
>> IIRC Transifex doesn't provide these features, while e.g. Crowdin and
>> TranslateWiki do. Have you considered either of them? Would it be feasible
>> to change the platform at this time?
>>
>> On Thursday, December 25, 2014 5:34:01 PM UTC, Ismael VC wrote:
>>>
>>> Merry Christmas everyone!
>>>
>>> I have an announcement and an invitation to make to the Julia community.
>>>
>>> Yesterday I finally finished seting-up, julialang docs on Transifex
>>> (online crowdsourcing localization platform) something I wanted to do ever
>>> since last year, but sadly never had time to actually invest on it, my
>>> intention is to translate the docs to spanish, and also make an invitation
>>> to anyone interested in helping me out or translating them to their native
>>> language.
>>>
>>> You can see my setup here: https://github.com/Ismael-VC/
>>> julia/tree/julia-translations/doc
>>>
>>> Please don't hesitate to ask me any question or give me advice I really
>>> want to do this well. If any of you have experience with any of this I
>>> would really really love to have a chat with you!
>>>
>>> ! I'm still testing the current setup (I don't know why `make gettext`
>>> takes so much time, yesterday it was done in a breeze:
>>>
>>> [ismaelvc@toybox doc]$ time ./update_resources.sh
>>> Enter passphra