MECHENG401:Meetings:7April
Jump to navigation
Jump to search
Attendance
- Gerald Weber
- Christof Lutteroth
- Shaun Seo
- Nick Irvine
- Mark Gardiner
- Patrick Cummuskey
- Jason Ingham
- Alistair Russell
- Matt Willacy
- Russell
- Oliver Browne
Discussion
- First the SE students presented a power point slide show on what we had done so far [to link...]
- Secondly, the CE students presented a photo slide show
- We got to see the kind of buildings they have been assessing
- We saw the kinds of damage they suffer and areas that contribute to lower strength
- There are problems analysing buildings that share walls with other buildings. Free standing buildings are much easier to analyse, and should be the ones we focus on as our 'test cases'. Harder buildings can come later.
- One of the buildings assessed was also assessed by an independent contractor, and the value calculated was different. This shows that some of the data that goes into an IEP is based on experience and extra knowledge/intuition.
- There are also problems analysing buildings that were built as one piece, but have since been sold off in sections to separate owners, as these separate parts may have been renovated at different times or in different ways, or parts not renovated at all.
- The purpose of the photos is to give someone enough information to analyse a building without having to go on-site and inspect it again. They should cover the interior, exterior and important points of interest/damage. A large building might require 20-25 photos, a smaller (average) building might require 10-15. These photos should be viewable inside the application in a slide show format.
- It would be nice to tag images/have a commentary box/store location + perspective data/store important notes. E.g "This photo shows the north wall of the building, note the water damage in the top left corner".
- All the councils plan records are digital, and so should be accessible through the application. These should be available in a separate frame/panel to the photos.
- Mailing list partly recorded, Nick Irvine to be responsible for group emails about meetings.
Timeframes
- Database backed app with basic functionality for recording the data.
- 3 weeks from now for an 'alpha' prototype for feedback
- 4 weeks from now for the final prototype
- Based on Patrick's paper prototype
- IEP module to do analysis and generate pdf reports is the next step
- Generates a report in pdf format, which is stored back in the database, and 'signed off' by the person who made it. Multiple copies of reports should be able to be stored, if many people generate reports using slightly different data.
- Based on Alistair's work on categorising un-reinforced masonry buildings, we may be able to make some refinements to the IEP process.
- End of semester, a fully functional system, without support for synchronisation
- End of the year, a fully functional system with support for synchronisation.