Skip to content

New package: Macchiato v0.2.0#149605

Closed
JuliaRegistrator wants to merge 1 commit intomasterfrom
registrator-macchiato-cd40ceae-v0.2.0-7fc42e987a
Closed

New package: Macchiato v0.2.0#149605
JuliaRegistrator wants to merge 1 commit intomasterfrom
registrator-macchiato-cd40ceae-v0.2.0-7fc42e987a

Conversation

@JuliaRegistrator
Copy link
Contributor

## Breaking changes

No breaking changes.

## Features

- Add Oceananigans-style `Simulation` API for running simulations
- Add linear elasticity model with boundary conditions and traction operators
- Add `zero_rows!` utility for O(nnz) sparse row zeroing
- Add Ferrite FEM cantilever beam example for comparison

## Performance

- Share KNN adjacency lists across operators and remove redundant weight updates

## Bug Fixes

- Fix mixed partial operator and body force sign in elasticity
- Handle `SparseVector` returned by RadialBasisFunctions for single evaluation points
- Fix variable naming and `Displacement` constructor in mechanics
- Correct Timoshenko analytical solution in beam example
- Thread RBF basis kwargs through to traction BC operators

## Refactoring

- Unify Dirichlet boundary conditions and simplify BC system with traits
- Remove legacy EquationSet BC compatibility system
- Move test dependencies to separate `test/Project.toml`

## Documentation

- Complete documentation overhaul with source-verified corrections
- Add Custom PDEs guide
- Update PhysicsDomain to EquationSet naming throughout

UUID: cd40ceae-7681-4e2e-9056-ba6e356aca3e
Repo: https://github.com/JuliaMeshless/Macchiato.jl.git
Tree: 17992297dc7a1cd88ec493eaca1f4c26166798f0

Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3
@github-actions
Copy link
Contributor

github-actions bot commented Mar 2, 2026

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. New package registration

Please make sure that you have read the package naming guidelines.

2. AutoMerge Guidelines are all met! ✅

Your new package registration met all of the guidelines for auto-merging and is scheduled to be merged when the mandatory waiting period (3 days) has elapsed.

3. To pause or stop registration

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

@goerz
Copy link
Member

goerz commented Mar 2, 2026

How does this relate to #149606? A v0.x seems much more appropriate to the apparent status of the project. In fact, it seems well on its way towards a v1.0 release

@JuliaTagBot JuliaTagBot added the AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. label Mar 2, 2026
@kylebeggs
Copy link
Contributor

@goerz we can close the previous in favor of this one. How do I reconcile the version in the Project.toml now?

@goerz
Copy link
Member

goerz commented Mar 2, 2026

I'd say, decide on which version you want to start with, which probably should be either v0.1, v1.0, or maybe v0.2 if you want to clarify what happened to v0.1 / retro-actively at a v0.1 tag to your repo. Set that version in your Project.toml, and then resubmit the registration. If you're going with v0.2, that'll simply update this PR to the latest commit (and I'll then unblock it to auto-merge in 3 days). If you decide on v0.1 or v1.0, it will create a new PR, and then I'll close both this PR and #149606 in favor of the new one.

[noblock]

@kylebeggs
Copy link
Contributor

Please close both PRs - I will create a new PR with 0.1. Thank you!

@kylebeggs
Copy link
Contributor

see #149638

@goerz
Copy link
Member

goerz commented Mar 2, 2026

Closing in favor of #149638

@goerz goerz closed this Mar 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. new package

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants