HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
yolhan83
BloodFlowTrixi.jl
Julia2025–2025
yolhan83 / BloodFlowTrixi.jl

BloodFlowTrixi.jl

This package implements 1D and 2D blood flow models for arterial circulation using Trixi.jl, enabling efficient numerical simulation and analysis.

Science & Engineering
Explore on GitHubRead Hacker News discussions
2Distinct people
2Mentions
0Explicit recommenders
0GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

This package implements 1D and 2D blood flow models for arterial circulation using Trixi.jl, enabling efficient numerical simulation and analysis.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 6-hour interval2 dated mentions

Observed mentions: 2025-02-15 22:36:17 UTC to 2025-02-20 11:00:36 UTC.

012025-02-15 18:00:00 UTC to 2025-02-16 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsFeb 15, 18:002025-02-16 00:00:00 UTC to 2025-02-16 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-16 06:00:00 UTC to 2025-02-16 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-16 12:00:00 UTC to 2025-02-16 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-16 18:00:00 UTC to 2025-02-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-17 00:00:00 UTC to 2025-02-17 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-17 06:00:00 UTC to 2025-02-17 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-17 12:00:00 UTC to 2025-02-17 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-17 18:00:00 UTC to 2025-02-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-18 00:00:00 UTC to 2025-02-18 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 18, 00:002025-02-18 06:00:00 UTC to 2025-02-18 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-18 12:00:00 UTC to 2025-02-18 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-18 18:00:00 UTC to 2025-02-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-19 00:00:00 UTC to 2025-02-19 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-19 06:00:00 UTC to 2025-02-19 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-19 12:00:00 UTC to 2025-02-19 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-19 18:00:00 UTC to 2025-02-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-20 00:00:00 UTC to 2025-02-20 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-20 06:00:00 UTC to 2025-02-20 12:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 20, 06:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 15, 18:002025-02-15 18:00:00 UTC2025-02-16 00:00:00 UTC110
Feb 16, 00:002025-02-16 00:00:00 UTC2025-02-16 06:00:00 UTC000
Feb 16, 06:002025-02-16 06:00:00 UTC2025-02-16 12:00:00 UTC000
Feb 16, 12:002025-02-16 12:00:00 UTC2025-02-16 18:00:00 UTC000
Feb 16, 18:002025-02-16 18:00:00 UTC2025-02-17 00:00:00 UTC000
Feb 17, 00:002025-02-17 00:00:00 UTC2025-02-17 06:00:00 UTC000
Feb 17, 06:002025-02-17 06:00:00 UTC2025-02-17 12:00:00 UTC000
Feb 17, 12:002025-02-17 12:00:00 UTC2025-02-17 18:00:00 UTC000
Feb 17, 18:002025-02-17 18:00:00 UTC2025-02-18 00:00:00 UTC000
Feb 18, 00:002025-02-18 00:00:00 UTC2025-02-18 06:00:00 UTC000
Feb 18, 06:002025-02-18 06:00:00 UTC2025-02-18 12:00:00 UTC000
Feb 18, 12:002025-02-18 12:00:00 UTC2025-02-18 18:00:00 UTC000
Feb 18, 18:002025-02-18 18:00:00 UTC2025-02-19 00:00:00 UTC000
Feb 19, 00:002025-02-19 00:00:00 UTC2025-02-19 06:00:00 UTC000
Feb 19, 06:002025-02-19 06:00:00 UTC2025-02-19 12:00:00 UTC000
Feb 19, 12:002025-02-19 12:00:00 UTC2025-02-19 18:00:00 UTC000
Feb 19, 18:002025-02-19 18:00:00 UTC2025-02-20 00:00:00 UTC000
Feb 20, 00:002025-02-20 00:00:00 UTC2025-02-20 06:00:00 UTC000
Feb 20, 06:002025-02-20 06:00:00 UTC2025-02-20 12:00:00 UTC101

What Hacker News says

2 sources
kjrfghslkdjfl·Feb 20, 2025
If the author is reading... Why specify compat in this manner? https://github.com/yolhan83/BloodFlowTrixi.jl/blob/03a78be28... Normally you want to specify "up to which major version" or "up to which (major, minor) version" your lib is compatible with, while allowing that all minor or path respectively are automatically upgraded. EDIT: To the person who said "Of all the languages, it often seems like Julia has the coolest libraries" It's just a very good language for writing libraries. Which is a crazy thing to say, because you're think that being good for writing libraries is something that every language would want to get exactly right, but it appears not.
In Bloodflowtrixi.jl – 1D and 2D blood flow models for arterial circulation

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.