Development Projects Page

I installed a few plugins to help manage tickets. Unfortunately it doesn't seem to currently support queries that involve creation dates… However the new Ticket Stats tab is somewhat useful to that end. By the way these charts are clickable!

"help_request", height=600, width=600, title = Open defects / help requests by priority )

TicketChart(type = pie, factor = owner, query=status=!"closed", height=600, width=600, title = Unclosed tickets by owner (includes enhancements))

Old Astrobear 1.0 issues

Introduction:The goal of this page is for people to suggest ways to improve AstroBEAR including known bugs that need fixing.

* To Do List *

iDivB == 2 (Dia and Woodward) needs 3D support: Look in problem.f90:afterfixup - should be fairly straightforward to implement.

InfoFieldUtils.f90 should be a module?: I believe Kris took a look at this when porting to bluehive?

iScheme==1 only supports ideal gas EOS or isothermal EOS: This involves finding pressure calculations and replacing them with calls to the pressure function

Unifying iScheme==0 and iScheme==1 to use same sections of code for solvers and eigensystems: They use different versions of common solvers, and don't both have access to the same collection of solvers.

Implementing Self-Gravity in AMR with Hypre: Gravity currently only works in a statically-defined refinement scheme; if grids move, unsightly cracking occurs.

Find a way to store "reverse" fixup fluxes: Currently, during each grid's update, it subtracts off the fluxes it eventually will add back in after it receives it's childrens fixup fluxes. This however, leaves the values for q in limbo between the grid's "timesteplevel" and it's "synchlevels". Currently algorithms that need access to updated values for q rely on allocating and updating a second copy of q (qfix). If instead of subtracting off the fluxes from q, each grid fully updated using all of the fluxes while storing the "reverse" fixup fluxes it would have subtracted and then later compare those with the fixupfluxes it receives from it's children, there would be no need for qfix. This in principle would involve less calculations and less memory (although the book-keeping would be a little tricky)

Stress test i_Protect.f90: Maybe run some very strong rarefactions that should create temperatures/pressures below the min value…

* Known Bugs *

iScheme==0,method(4)==2 does not behave properly with source terms and amr: Someone will have to explain to me how this algorithm is supposed to work (jjc)

MinTemp not used consistently: There seems to be confusion with the temperature floor used for pressure protections, for cooling cut-off, (and for an Isothermal sound speed)

iProtect (or some mysterious force) causes occasional unnatural explosions: We've all seen 'em - most recently in Sean's single clump cooling runs at very high densities