Skip to content

Conversation

@exaexa
Copy link
Member

@exaexa exaexa commented Aug 21, 2025

I decided to clean gigasom up a little, for reasons.

This will include some (minor) API changes so that stuff is compatible with the latest julia standards and modern CI etc. For that reason it's gonna be gigasom 1.0 (finally!)

TODOs:

  • README cleaning
  • 💯% coverage

@exaexa
Copy link
Member Author

exaexa commented Aug 21, 2025

cc @oHunewald I think this is good to do before we base any work on this (also, we can intern the data export functions etc. in this)

@exaexa exaexa changed the title massive cleanup, v2 massive cleanup + stabilization Aug 21, 2025
@exaexa exaexa requested a review from oHunewald August 27, 2025 14:03
@codecov
Copy link

codecov bot commented Nov 3, 2025

Codecov Report

❌ Patch coverage is 65.33333% with 26 lines in your changes missing coverage. Please review.
✅ Project coverage is 76.79%. Comparing base (1fff45f) to head (7ac1aa3).

Files with missing lines Patch % Lines
src/load.jl 37.03% 17 Missing ⚠️
src/som_utils.jl 50.00% 6 Missing ⚠️
src/data_utils.jl 75.00% 2 Missing ⚠️
src/split.jl 50.00% 1 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##           master     #212       +/-   ##
===========================================
- Coverage   93.68%   76.79%   -16.90%     
===========================================
  Files           9        8        -1     
  Lines         412      405        -7     
===========================================
- Hits          386      311       -75     
- Misses         26       94       +68     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

#
# First, load GigaSOM:

using GigaSOM
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It may sound a bit petty but I would stick with one style in the documentation, as above "import GigaSOM"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants