Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Nov 21 2021 16:20
    serge-hulne closed #36
  • Nov 21 2021 15:34
    serge-hulne edited #36
  • Nov 21 2021 15:29
    serge-hulne opened #36
  • Mar 29 2020 08:41

    watzon on master

    Update FUNDING.yml (compare)

  • Jan 29 2020 04:24
    watzon closed #35
  • Jan 29 2020 04:24
    watzon commented #35
  • Jan 21 2020 22:37
    Calamari commented #35
  • Jan 21 2020 20:09
    watzon commented #35
  • Jan 21 2020 18:28
    Calamari edited #35
  • Jan 21 2020 18:27
    Calamari opened #35
  • Nov 11 2019 19:58
    watzon commented #30
  • Nov 11 2019 19:20
    rmarronnier commented #30
  • Nov 07 2019 23:07
    watzon unlabeled #34
  • Nov 07 2019 23:07
    watzon unlabeled #33
  • Nov 07 2019 23:07
    watzon labeled #33
  • Nov 07 2019 23:07
    watzon unlabeled #33
  • Nov 07 2019 23:06
    watzon labeled #34
  • Nov 07 2019 23:06
    watzon labeled #34
  • Nov 07 2019 23:06
    watzon labeled #33
  • Nov 07 2019 23:06
    watzon labeled #33
Rémy Marronnier
@rmarronnier
*class
Chris Watson
@watzon
In the case of TfIdf, Sentiment, etc which only have one class we should probably just keep it a top level class. Unless you have a better idea.
Rémy Marronnier
@rmarronnier
oh, I see, if we make sentiment a module, we'll have Cadmium::Sentiment::Sentiment. Stutterall over again. You're right. No children, no module.
Chris Watson
@watzon
Yeah exactly
Rémy Marronnier
@rmarronnier
New PR done :-)
Chris Watson
@watzon
Got it
Chris Watson
@watzon
I've signed cadmium up for the github actions beta
As soon as it gets approved I want to move the CI stuff from Travis to there
Rémy Marronnier
@rmarronnier
Great, I've never done CI stuff. It's gonna be fun :-)
Chris Watson
@watzon
Should be pretty similar to the Travis stuff that's already in there
Rémy Marronnier
@rmarronnier
Ok, I'll look at that.
Chris Watson
@watzon
We could actually integrate this into Cadmium as well. I think it's got some things that the Transliterator doesn't have
Rémy Marronnier
@rmarronnier
Looks useful. What do you want to do? Have a Cadmium::sterile shard ? Insert some methods into the transliterator ?
Rémy Marronnier
@rmarronnier
Also,I've looked into Stanford vs Cadmium Glove files format and :
  • I don't have the skills nor the motivation to write a converter in Crystal the binary files of the coincidence matrices output by Stanford.
  • However, I could write an adapter to read the .txt files.
  • For this to be useful, Cadmium::Glove should be able to start a training with word-vectors.json and corpus.json but without the coincidence matrix. Do you have any plans for this ?
Chris Watson
@watzon
I don't, so don't worry about it for now haha
As far as Sterile, I was thinking it could be merged with the Transliterator
Rémy Marronnier
@rmarronnier
Yeah, go for it ! :D
The more I read about POS tagging, the more I think we need to port Keras to crystal lol I'm going crazy :-p
Chris Watson
@watzon
It would be a really nice thing to have
Rémy Marronnier
@rmarronnier
Yeah, it's weird Python has all the nice toys. I was expecting the Go or Rust community to build the state of the art ML tools... but no.
Chris Watson
@watzon
Everyone is comfortable with Python and its ease of use
Which sucks
But gives us an opportunity in Crystal :wink:
Rémy Marronnier
@rmarronnier
Exactly ! I can't wait for the 1.0 to come out, just to be taken seriously by companies
Chris Watson
@watzon
Me too
Rémy Marronnier
@rmarronnier
Oh github actions is on !
I've set it up for lemmatizer (without ameba though) and test with my next PR :-)
*will test
Chris Watson
@watzon
Awesome :)
Yay Github Actions! I'm going to try setting up the CI with one of the libraries
Rémy Marronnier
@rmarronnier
Yeah ! So easy to set up :-) Great idea mate
Chris Watson
@watzon
Super easy, just one file change
weird... it worked before
Chris Watson
@watzon
Nice that the Lemmatizer is passing. Let's make sure that all of the libraries have ameba installed as a development dependency and then use the same configuration file as cadmiumcr/cadmium
Rémy Marronnier
@rmarronnier
ok !
Rémy Marronnier
@rmarronnier
Just so you know, https://cadmium.ml/ is down
Chris Watson
@watzon
Uh oh haha
I'll look into it
Reallyweird. I don't have this issue locally for the same repo.
Chris Watson
@watzon
You might be running a lower Crystal version. That error was introduced in 0.30.1 I believe
Maybe 0.30.0
Rémy Marronnier
@rmarronnier

`Crystal 0.30.1 [5e6a1b672] (2019-08-12)

LLVM: 4.0.0
Default target: x86_64-unknown-linux-gnu`

Chris Watson
@watzon
Also I'm pretty sure I fixed that error. Maybe the shard.lock is out of date.
Try deleting it, running shards install, and recomitting
Rémy Marronnier
@rmarronnier
But the shards.lock is not comitted and github actions does a fresh shards install every time