Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Apr 22 20:22
    abhinavchawla starred JuliaReach/LazySets.jl
  • Apr 22 19:36

    mforets on gh-pages

    build based on a2c83b1 (compare)

  • Apr 22 19:09
    SebastianGuadalupe opened #127
  • Apr 22 19:08

    SebastianGuadalupe on concreteReLU

    add concrete ReLU Solver (compare)

  • Apr 22 18:56

    mforets on gh-pages

    build based on c55a502 (compare)

  • Apr 22 18:52

    mforets on gh-pages

    build based on d7bcc87 (compare)

  • Apr 22 18:28
    schillic synchronize #126
  • Apr 22 18:28

    schillic on 122

    add test context for #122 (compare)

  • Apr 22 18:26
    schillic opened #126
  • Apr 22 18:25

    schillic on 122

    add test context for #122 (compare)

  • Apr 22 11:04
    mforets synchronize #2672
  • Apr 22 11:04

    mforets on 2671

    Update test/Sets/HalfSpace.jl … (compare)

  • Apr 22 10:57
    mforets opened #2672
  • Apr 22 10:56

    mforets on 2671

    add rationalizion for LazySets (compare)

  • Apr 22 09:25
    mforets assigned #2671
  • Apr 22 09:24
    mforets labeled #2671
  • Apr 22 09:24
    mforets opened #2671
  • Apr 21 19:47

    mforets on gh-pages

    build based on 27a73225 (compare)

  • Apr 21 19:30

    mforets on gh-pages

    build based on 27a73225 (compare)

  • Apr 21 19:29

    mforets on gh-pages

    build based on 09107240 (compare)

Marcelo Forets
@mforets
a new article on verifying LTI systems neural network controllers https://arxiv.org/pdf/2101.01815.pdf
Marcelo Forets
@mforets
hi, this week i'm back to package development. i was planning to address the Star sets implementation this afternoon. i've got like 2 hours :smile:
Christian Schilling
@schillic
good luck :)
Marcelo Forets
@mforets
there is a nice boost on the startup time:
[mforets@localhost bin]$ julia
               _
   _       _ _(_)_     |  Documentation: https://docs.julialang.org
  (_)     | (_) (_)    |
   _ _   _| |_  __ _   |  Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 1.5.2 (2020-09-23)
 _/ |\__'_|_|_|\__'_|  |  Official https://julialang.org/ release
|__/                   |

julia> @time using LazySets
  5.681156 seconds (11.94 M allocations: 694.502 MiB, 4.23% gc time)

julia> exit()
j[mforets@localhost bin]$ ./julia
               _
   _       _ _(_)_     |  Documentation: https://docs.julialang.org
  (_)     | (_) (_)    |
   _ _   _| |_  __ _   |  Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 1.6.0-beta1 (2021-01-08)
 _/ |\__'_|_|_|\__'_|  |  Official https://julialang.org/ release
|__/                   |

julia> @time using LazySets
  2.215739 seconds (5.24 M allocations: 375.817 MiB, 1.47% gc time, 0.22% compilation time)
Marcelo Forets
@mforets
i merged some LazySets PRs without waiting for the travis CI to finish . this is against our rules i know ... but we can't wait 40 mins - 1hour for each single PR it is just too slow. maybe if we change the CI to github actions it reduces
in RA it reduced the waiting time by half
or we get a university machine to run the tests and upload the results in less than 10 minutes
is that possible? for the machine i can ask @dfcaporale
Marcelo Forets
@mforets
it would be limited to only 1 platform though, but that is less of a problem (we don't have system-specific code, but some of our optional dependencies do)
Christian Schilling
@schillic
for me waiting one hour is not a blocker because 1. most often the branches are independent and if not then 2. i can merge the branches into other branches locally, so i don't have to wait for CI to finish to continue developing. but i don't want to impose that
about github actions: would be great :)
Marcelo Forets
@mforets
you're absolutely right. sometimes it feels like having 3 approved PRs waiting the CI to finish (and you know it's OK 99%) is too much
there's satisfaction if you can close issues before you call it a day :laughing:
Christian Schilling
@schillic
true :)
Marcelo Forets
@mforets
but, yeah anyway there is plenty of advantage of having these online tools, for example that they provide hyperlinks to each line of the build
this tends to be very useful when there are issues
Christian Schilling
@schillic
how much work is it to try github actions?
Marcelo Forets
@mforets
i would be happy if we are able to setup a github action locally (whatever that means) and have a bot that comments that the tests passed or not, maybe with a log but that may be harder. i'm unfamiliar to this stuff but maybe there are examples that we can replicate
Christian Schilling
@schillic
but you said you did it in RA?
Marcelo Forets
@mforets
ah
yes it is done
i thought you meant something local
for the github actions it is easy
Christian Schilling
@schillic
no no
is there a reason why we don't have it in LazySets?
Marcelo Forets
@mforets
it should be
2) delete .travis.yml
that was it iirc
Christian Schilling
@schillic
:)
maybe let's first try github actions :)
Marcelo Forets
@mforets
yes
:)
that build_private script
i dont know how to implement it in the github action script
Christian Schilling
@schillic
ah :(
we will remove it once we pass to v1.6 only
Christian Schilling
@schillic
true
Marcelo Forets
@mforets
we can wait until then :)
Christian Schilling
@schillic
good :)
Marcelo Forets
@mforets
postponing things is a good tactic :laughing:
Christian Schilling
@schillic
^^
Marcelo Forets
@mforets
i think we should just bump the minimum julia version to 1.5 in the LazySets CI
Christian Schilling
@schillic
Marcelo Forets
@mforets
:thumbsup: