Eric To Do: Difference between revisions

From bone.wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(40 intermediate revisions by the same user not shown)
Line 1: Line 1:
==Soon==
==Soon==


Build ParaView 3.8.1 with mpi support.
* Contact Peter Cripton (talk to Steve first)
 
* Check progress of backup.
Investigate load times for AIM files in ParaView.
* Agreement to sell FAIM.
 
* Timesheets - back dated.
FAIM: make sure that force constraints are correct.  (Need to have vtkskiFiniteElementModel generator that applies constant body force?? or pressure??)
* spreadsheet for licenses
 
* Wiki page for customer information
Material models: need string constants instead of integer constants (possibly they exist already for C++, but need Python versions.)
* Numerics88 wiki - support for source tag.
 
* extra drives for SmartStor?
FAIM: all output to current directory.
* Open directory for logging into lab computers.
 
* Numerics88 subversion repository - line endings automatically match client system.
Bending test: does not work very well for data sets with large offset (i.e. test25a.aim).  Solution: Need to be able to specify not just neutral axis angle, but entire neutral axis vector.  Also, probably want one surface fixed, and the other surface to have force conditions.
 
comparative functional tests (ie. compared to a previously-run functional test).  Sharing a common base test class with compare_to_fe_by_assembly.  This would be useful for multithreaded vs. singlethreaded.
 
Steve: where are test75, etc?
 
faim: svn revision number (then report this in functional tests)
 
functional tests: anisotropic
 
functional tests: multithreaded solutions
 
functional tests: a test case for rotated tests (i.e., same thing, but rotated so along x,y,z axes).  Or alternatively just apply force along different axis.
 
functional tests: force constraints
 
faim: transverse constraints for standard tests. i.e. pivot points.
 
faim: license file
 
faim: cmake installation to destination
 
faim: compare speed of new build to old build.
 
Backup drive.
 
Gaussian Filter in ParaView is working?  not really - maybe in 3.8.1?
 
Test network speed between mighty-mac and mike .
 
AIMSimilarityRegistration.cxx : working?
 
AppPointPicker (name??) works on OS-X?
 
vtkski: test installation.
 
vtkTensorOfInertia:
# get principle axes
# accept weights (as pointer) - or use scalars as default??
# test cases
# treat voxels as boxes instead of points
# accept UnstructuredGrid input (someday)
 
Carolyn : list of programs.
 
Add section to wiki about:
1. Basic CMake usage
2. common development directories (/usr. /opt, etc...)
 
Try build of vtkski/ParaView with spaces in directory names.
 
ParaView build with vtkski included, Windows.
 
Binary build of vtkski?  (Including all Applications.)
 
Westgrid account.
 
Make OrientationParameters a class (in vtkMeshGenerator).
 
Take Scoliosis thesis to Ivan.
 
vtkImageToMesh: Need to return some sort of structure that stores (1) the integer location of nodes, (2) sets of nodes on surfaces.  Maybe just (1) for vtkImageToMesh, stored as a DataArray on the points. The (2) could be generated in vtkGenerateMesh??
 
Functional tests for vtkMeshGenerator (or maybe they are unit tests).
 
vtkMeshModel: Create Functions AddSingleConstraint.  This will add a single displacement/force constraint.  Possibly there will be a dedicated named selection for all of these.
 
Faim memory:
* reporting
* limiting (e.g. faim -memlimit 4GB somemodel.inp)
* estimating (e.g. faim -estimate somemodel.inp)
 
vtkskiMeshModel : no longer separately encode Restraints and Displacements (Restraints are just 0-valued Displacements).
 
compile AIX for OS-X .


==Medium Term==
==Medium Term==


Migrate high priority vtkMy apps with ITK.
* Bonelab Wiki: Add list of applications for bonelab tools.
 
* AIX and AIMOD into vtkski.
Migrate high priority vtkMy apps with Qt.
* Gaussian Filter in ParaView is working?  not really - maybe in 3.8.1?
 
* Migrate high priority vtkMy apps with ITK.
Find out why vtkImagePurify appears to do nothing.
* Migrate high priority vtkMy apps with Qt.
 
* itk Reader/Writer for AIM (and remove VTK dependencies for apps that use only this VTK item).
Find out why vtkFairSmooth appears to do nothing.
* Revision number in main page of vtkski doxygen documentation.
 
Analytic expression for orthotropic element stiffness matrix elements.
 
Work out boundary values that arise from integration by parts in analytic expression for element stiffness matrix elements.
 
Get test data for aimpack_test?
 
MeshGenerator: split into
# Generic Mesh Generator (no boundary conditions)
# Standard Models Generator (probably a base class and subclasses)
 
Split faim FE solver and analysis into two separate programs.
 
Make sure that all Test programs can be run unmodified when moved out of the vtkski source tree.
 
DOxygen documentation for itkski
 
Fix up itkAIMImageIO.
 
itk Reader/Writer for AIM (and remove VTK dependencies for apps that use only this VTK item).
 
Submit conf_parser to boost??
 
Change all vtkski / Applications to use boost::program_options
 
Revision number in main page of vtkski doxygen documentation.
 
Evaluate possible speed gain of eliminating device syncs in faim/GPU.
 
Evaluate double-precision speed of faim on Westgrid hardware.
 
Make a vtkFAIMInputReader class.
 
Compile faim on WestGrid.
 
Move plane intersection functions out of vtkMeshGenerator into their own filter(s).
 
faim: accelerate post-processing
 
Rewrite faim in C++.
 
vtkski: cmake copy all headers to 'include' directory in build directory.


==Someday==
==Someday==


FAIM: Ever need models with 64 bit indexing?? (i.e. more than 2^32 nodes or elements)
* mighty-mac and mavis: reconfigure disks into a single striped RAID array (hence users don't have to think about using /Volumes/localdata).
 
* ParaView: Registration Plugins (a modification of one of http://paraview.org/Wiki/User_Created_Plugins ?)
FAIM: km generation should be function (or even better, class) - should allow two flavors:
* Speed tests for ifdutil and faim in general.
# S&G style numerical integration
# my analytic expression
 
CPU affinity for multithreading in FAIM  (NUMA)
 
MPI solver for faim
 
FAIM: partitioner based on 3D geometry (ie. noninductive sets based on 27 nearest neighbours + center).
 
Paraview: Create Mesh Model (including custom constraints) within ParaView
 
CMake: Install destination for vtkski, etc....
 
CMake: Binary Installer for vtkski, etc...
 
ParaView: Registraion Plugins (a modification of one of http://paraview.org/Wiki/User_Created_Plugins ?)
 
Speed tests for ifdutil and faim in general.


==Random Ideas==
==Random Ideas==
New file format for faim.  Either a more robust text format (with optional binary sections), or something like NetCDF/HDF5.

Latest revision as of 20:59, 12 May 2011

Soon

[edit]
  • Contact Peter Cripton (talk to Steve first)
  • Check progress of backup.
  • Agreement to sell FAIM.
  • Timesheets - back dated.
  • spreadsheet for licenses
  • Wiki page for customer information
  • Numerics88 wiki - support for source tag.
  • extra drives for SmartStor?
  • Open directory for logging into lab computers.
  • Numerics88 subversion repository - line endings automatically match client system.

Medium Term

[edit]
  • Bonelab Wiki: Add list of applications for bonelab tools.
  • AIX and AIMOD into vtkski.
  • Gaussian Filter in ParaView is working? not really - maybe in 3.8.1?
  • Migrate high priority vtkMy apps with ITK.
  • Migrate high priority vtkMy apps with Qt.
  • itk Reader/Writer for AIM (and remove VTK dependencies for apps that use only this VTK item).
  • Revision number in main page of vtkski doxygen documentation.

Someday

[edit]
  • mighty-mac and mavis: reconfigure disks into a single striped RAID array (hence users don't have to think about using /Volumes/localdata).
  • ParaView: Registration Plugins (a modification of one of http://paraview.org/Wiki/User_Created_Plugins ?)
  • Speed tests for ifdutil and faim in general.

Random Ideas

[edit]