- This topic has 2 replies, 2 voices, and was last updated 10 years, 9 months ago by Ryan Moore.
-
AuthorPosts
-
January 28, 2014 at 8:07 pm #4117Ryan MooreKeymaster
Any improvement you can make you can model! The 50% improvement is a default measure for which we have estimated cost information. The actual improvement savings are based on the numbers that you input into the cfm25 controls. If you select the 50% improvement, but then change the target improved cfm25 to what would be a 75% improvement over the base cfm25, then that is what drives the modeled savings. In that case you would want to edit the job cost., either on the bid sheet or using the cost override.
Additionally, you may add your own custom improvement options to the database with other % reductions in leakage and add your own costs. You can create a new measure using the add/edit items dialogue (“>” button to the right of the improved duct leakage control). These new items will always be available for you to select in the future.
January 29, 2014 at 7:09 am #4304Kevin JacksonParticipantWhen I tried to make a new measure, the system has the following Application Error which I submitted yesterday but didn’t include a copy of the details but here they are:
Unexpected OptiMiser Exception:
Abort due to constraint violation
column TemplateCostID is not uniqueSystem.Data.SQLite.SQLiteException
Stack Trace:
at System.Data.SQLite.SQLite3.Reset(SQLiteStatement stmt)
at System.Data.SQLite.SQLite3.Step(SQLiteStatement stmt)
at System.Data.SQLite.SQLiteDataReader.NextResult()
at System.Data.SQLite.SQLiteDataReader..ctor(SQLiteCommand cmd, CommandBehavior behave)
at System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior)
at System.Data.SQLite.SQLiteCommand.ExecuteScalar()
at OptiMiser.SQLEditorDialog.InsertRowGetId(SQLiteConnection conn, String insertStatement, DataRow row)
at OptiMiser.SQLEditorDialog.CopyRow(DataRow row)
at OptiMiser.SQLEditorDialog.NewButton_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)Note that you can press the PrtScr key to take a snapshot of this message; you can also Copy/Paste its contents
February 21, 2014 at 7:08 am #4334Ryan MooreKeymasterThis has been fixed in version 3.0.4x.
-
AuthorPosts
- You must be logged in to reply to this topic.