PeerMeeting: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
(5 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
== | == PEER == | ||
proposal/document outlining what we are going to do to meet their list of shortcomings. | |||
# Better documentation in wiki format for both modeling and analysis to adderess concerns over poor documentation and difficulty developers have in getting documentation uploaded. | |||
## User requirements doc. | # Best of practice examples for industry users. | ||
# User requirements doc. | |||
# OpenSees Lite - fewer choices with validated models | |||
# Educate Users | |||
## voice-over workshop slides | |||
## fcf on nonlinear analysis video | |||
## Better documentation | |||
# Data Output to database - better doc & test usability. | |||
# Possible GUI - Mahmoud to look at existing | |||
# For next release - registration update & surveymonkey before get to code when user hit download button. | |||
# Regular Webex meeting with Users! | |||
== [[NEES Proposal]] == | |||
== NOTES FROM PEER MEETING == | == NOTES FROM PEER MEETING == |
Latest revision as of 19:54, 30 November 2009
PEER
proposal/document outlining what we are going to do to meet their list of shortcomings.
- Better documentation in wiki format for both modeling and analysis to adderess concerns over poor documentation and difficulty developers have in getting documentation uploaded.
- Best of practice examples for industry users.
- User requirements doc.
- OpenSees Lite - fewer choices with validated models
- Educate Users
- voice-over workshop slides
- fcf on nonlinear analysis video
- Better documentation
- Data Output to database - better doc & test usability.
- Possible GUI - Mahmoud to look at existing
- For next release - registration update & surveymonkey before get to code when user hit download button.
- Regular Webex meeting with Users!
NEES Proposal
NOTES FROM PEER MEETING
OpenSource
- Engage community spirit
- Recognize limitations of open-source with regards to research based fe code
- Developers typically students who leave
- Developers working on individual classes
- Limited follow-up on fixes, maintenance and support after submission of code
- Given limitations how can we help.
PEER document outlining problems with OpenSees from a users point of view created by outside consultant and OpenSees guru (Z.Yang - ucsd!)
- Solution Documentation
- User Command and Examples Manuals.
- ??
- Updated tech Manual.
- GUI
Users:
- We need an integrated user environment for PBEE design methodology from NGA database to fragility curves.
- User Requirements doc. Where do we get the requirements?
- Projects currently funded
- Anybody who might get a project
- NEES user forum
- Survey (surveymonkey)
- Questionaires at meetings
- Industry
- Documentation, Training & Outreach
- wiki
- PEER to provide student for moving current documentation
- Video-lecture library
- Filip nonlinear analysis video
- Links to papers (.pdf viewing in wiki)
- Productivity modules
- wiki
- GUI
- mahmoud to look at existing ones and comment.
- Interface with existing GID, GSA
- Develop new - ship to India
- look into commercial alliance
- damage visualization
- OpenSees Lite
- Verification (could do color coding in wiki Green, Orange, Red of command)
- Database Usage in recorders
- Integration with BIM?
Developers:
- How to engage
- Carot & Stick
- If OpenSees more popular .. fact code in or code ranking, download count.
- Sell .dll
- institute a Developer Task Force with regular meetings
- coordination
- How to give developers kudos
- Website count downloads.
- Website Ranking