Introduction
Summary of Progress
- There is only a small amount of progress to report with regard code development in this period
- There has been a re-organisation of how the Household SAR data are stored and accessed
- This has provided convenience and efficiency gains
- It is now straightforward to look up other members of a household given a HRP
- Random selections of HRPs for specific AGEH groups can be returned
Details of work and problems encountered and things to do
- Previosly Household SAR data was reordered and stored in multiple files giving the option for the data to be read directly from these formatted fileds rather than being stored in fast access memory
- Such data handling is advantageous if fast access memory is very limited
- It is now asumed that there is sufficient fast access memory to store the Household SAR in an Array
- As the Household SAR source data are read
- A Random number of either 0 or 1 is added to AGEH
- The resulting AGEH and HRP status are then stored as keys for a HashMap collection, the values of which are references to the Array of Household SAR records
- Another HashMap collection is used to store the look up to other household members from an HRP, keys are references to HRPs in the Array of Household SAR records, values are references to the Array of Household SAR records
- Adding a Random number of either 0 or 1 is added to AGEH has made subsequent coding much easier
- After investigation, previously attempts made to aggregate to common age group boundaries for constraints (controls) were deemed undesirable
- Next Steps
- Configure IndividualCensus class to use the new convenience methods for accessing Household SAR data