Open nikhilgupta10 opened 8 years ago
nikhilgupta10 imported these comments from Sourceforge: The user dchassin does not exist anymore. Therefore assigning this to afisher1. "dchassin": * owner changed from jcfuller to dchassin
status changed from new to accepted ,
"dchassin": * owner changed from dchassin to jcfuller
Can we get a summary of the appliances in 2.3 from the standpoint of status? Which have completed requirements, specifications, implementation and validation? Once we have that information, I will write the updates to the wiki docs for 2.3.
,
"dchassin": * type changed from enhancement to task ,
"dchassin": * owner changed from jcfuller to dchassin
Documentation must be updated to reflect the following supported functionality:
,
"dchassin": * priority changed from minor to major
Updated the following docs to identify in which version the various appliance are validated and supported.
- https://sourceforge.net/apps/mediawiki/gridlab-d/index.php?title=Residential_%28module%29
Although the appliances are mentioned in the requirements, specification, developer notes, and technical support docs, there is no need to indicate in which version of GridLAB-D the requirements, etc. are satisfied.
Noted is the complete lack of a validation document, a problem which goes to heart of this ticket. For this reason, this ticket is being passed forward to trunk for more thorough resolution.
,
"dchassin": * owner changed from dchassin to andyfisher
This is caused by internal_syncall() returning hard events for things that should be soft events (e.g., enduse, loadshape). The fix is offered as part of #591 in r3951.
Unfortunately, this reveal 2 additional autotest errors in #591.
,
"dchassin": * owner changed from andyfisher to dchassin
Disregard last posting. That was meant for #648.
,
"dchassin": * status changed from assigned to accepted ,
"dchassin": * milestone changed from Version 3.0 RC 1 to Unscheduled ,
"dchassin":- Milestone: Unscheduled --> Version 4.0 RC1 ,
There is some confusion about what will be supported around the residential appliance loads. We should document the requirements for the appliance objects (e.g., freezer has a physical model, so should it also support a generic loadshape?, what about the waterheater which converts the loadshapes to a water_demand?) and start moving towards implementing the requirements.
,