Changes between Version 51 and Version 52 of Czarships/Development
- Timestamp:
- 02/18/14 13:03:41 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Czarships/Development
v51 v52 2 2 = Development Team = 3 3 4 For information on bugs and development projects consult the [http://clover.pas.rochester.edu/trac/astrobear/report ticketing system]. 5 6 For a complete list of open development tickets see [report:30 this report] 7 8 [GoldenVersion Golden Version] -- !Modules/Features should go to Golden Version AstroBEAR2.0 9 10 [FeatureMatrix Feature Matrix] -- Matrix showing features and their status 11 12 [DevelopmentProcedure Development Procedure] -- Proper procedure for altering or adding new code to AstroBEAR 13 14 15 [CodeDeveloperLogs Old Developer Logs] -- Includes development issues, compilation problems and run-time difficulties 16 4 * For information on bugs and development projects consult the [http://clover.pas.rochester.edu/trac/astrobear/report ticketing system]. 5 * For a complete list of tickets assigned to the Development Team see [report:30 this report] 6 * For a complete list of enhancement tickets see [report:31 this report] 7 * [GoldenVersion Golden Version] -- !Modules/Features should go to Golden Version AstroBEAR2.0 8 * [FeatureMatrix Feature Matrix] -- Matrix showing features and their status 9 * [DevelopmentProcedure Development Procedure] -- Proper procedure for altering or adding new code to AstroBEAR 10 * [CodeDeveloperLogs Old Developer Logs] -- Includes development issues, compilation problems and run-time difficulties 11 * [OldAstrobearIssues Old Astrobear Issues] -- Legacy page 17 12 [[br]] 18 13 … … 26 21 From [topic:26 Phase III ideas] 27 22 28 * Create a standard interface for module objects (clumps, winds, backgrounds, etc...)23 * ~~Create a standard interface for module objects (clumps, winds, backgrounds, etc...)~~ 29 24 {{{ 30 25 CreateObject … … 38 33 }}} 39 34 40 * Create ErrFlag modules for refining on jeans length, cooling length, field gradients, etc... so that any problem module can easily use these.35 * ~~Create ErrFlag modules for refining on jeans length, cooling length, field gradients, etc... so that any problem module can easily use these.~~ 41 36 42 * Turn initambient into a background type object module that can be called from the problem module. That way users can calculate background densities within their problem module etc... (and we can get rid of modules.data)37 * ~~Turn initambient into a background type object module that can be called from the problem module. That way users can calculate background densities within their problem module etc... (and we can get rid of modules.data)~~ 43 38 44 * Allow module control to keep track of the order that objects are created - or assign each object a creation number - so that objects that overlap - will be called in a user specified order... (Winds and colliding flows are both used by the MolecularCloudFormation module - but it requires windbeforestep to be called before collidingflowbeforestep for example)39 * ~~Allow module control to keep track of the order that objects are created - or assign each object a creation number - so that objects that overlap - will be called in a user specified order... (Winds and colliding flows are both used by the MolecularCloudFormation module - but it requires windbeforestep to be called before collidingflowbeforestep for example)~~ 45 40 46 41 * Create a web interface where users can create objects - which then get passed to a series of scripts which create a problem module - and start the code at a low resolution to output the first frame - which then gets processed by bear2fix to spit back an image - so the user can see their problem setup on the fly. 47 42 48 * Create processing modules that can be called during the run or after the run completes - but that are built into AstroBEAR. This way they can use the same IO routines and can easily be run in parallel - on the same system the simulation is run on. This will avoid massive data storage and transportation.43 * ~~Create processing modules that can be called during the run or after the run completes - but that are built into AstroBEAR. This way they can use the same IO routines and can easily be run in parallel - on the same system the simulation is run on. This will avoid massive data storage and transportation. ~~ 49 44 50 45 * Preallocate sweep buffers for the entire level - instead of individually for each grid? 51 46 52 * Reorder sweep direction to operate on contiguous memory blocks47 * ~~Reorder sweep direction to operate on contiguous memory blocks~~ 53 48 54 * Move all protection routines/pressure calculations/conversion between conservative and primitive variables/ to the EOS module (instead of the sweep module and the riemann_solvers module).49 * ~~Move all protection routines/pressure calculations/conversion between conservative and primitive variables/ to the EOS module (instead of the sweep module and the riemann_solvers module).~~ 55 50 56 51 * Clean up the sweep module so that different stages of the update are separated into different subroutines... … … 60 55 * Add pencil method for directionally split schemes? Or create different stencil sets for different combinations of directional ordering (x-y-z, y-z-x, etc...) 61 56 62 * Update limiter method to reduce mbc (Colella and Sekora 2008)57 * ~~Update limiter method to reduce mbc (Colella and Sekora 2008)~~ 63 58 64 59 * Convert variables that are constant for each run into Parameters that are set by a configure script at build time... (nDim, lMHD, MaintainAuxArrays, iSolver, iEOS, etc...) 65 60 66 61 67 = Also see =68 [report:31 Active enhancement tickets]69 62 70 63 … … 72 65 [[CollapsibleStart(Old Astrobear 1.0 issues)]] 73 66 74 = Old Astrobear 1.0 issues = 75 '''Introduction''':The goal of this page is for people to suggest ways to improve AstroBEAR including known bugs that need fixing. 76 77 == *** To Do List *** == 78 '''iDivB == 2 (Dia and Woodward) needs 3D support''': Look in problem.f90:afterfixup - should be fairly straightforward to implement. 79 80 '''InfoFieldUtils.f90 should be a module?''': I believe Kris took a look at this when porting to bluehive? 81 82 '''iScheme==1 only supports ideal gas EOS or isothermal EOS''': This involves finding pressure calculations and replacing them with calls to the pressure function 83 84 '''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. 85 86 '''Implementing Self-Gravity in AMR with Hypre''': Gravity currently only works in a statically-defined refinement scheme; if grids move, unsightly [CrackingImage cracking] occurs. 87 88 '''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) 89 90 '''Stress test i_Protect.f90''': Maybe run some very strong rarefactions that should create temperatures/pressures below the min value... 91 92 [[br]] 93 == *** Known Bugs *** == 94 '''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) 95 96 '''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) 97 98 '''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 67 99 68 [[CollapsibleEnd]] 100 69 [[BackLinks]]
