KarstModel / scallop-abrasion

Code for dissertation chapter on scallop abrasion
MIT License
1 stars 0 forks source link

Long-term wish list #11

Open KarstModel opened 3 years ago

KarstModel commented 3 years ago
ddoubleprime commented 3 years ago

Periodic boundaries are a good idea, shouldn't be hard to implement, and developing them will probably catch some bugs we've been missing.

Acknowledging this is a long term wish list, but this applies to the other thread too:

Bear in mind the initial conceit is that we are looking at the pattern of representative particle trajectories, one per start location on the x axis at a specified height. That follows from the assumptions of Lamb et al. Is that compatible with then taking those representative paths to initialize a full-blown particle-tracking-and-rebound simulation? There are faster codes that do that and in turbulent flow to boot.

It may become important to define a really restrictive initial scientific goal for this model, at which point you stop developing and publish, because the temptation is to keep bolting more and more features on until you've made your own StarCCM+ but slower cuz Python.

KarstModel commented 3 years ago
  1. bug hunt, 2. goal definition