Bug #5263
closedfailure to restart after upgrade from 2.0 to 2.1
0%
Description
You are receiving this mail because Pranav Godbole
ingi_05@hotmail.com
is sending feedback about the site administered by you at https://kepler-project.org.
The message sent was:
Hello, I'm having some difficulty updating from 2.0 to 2.1 on Windows 7. After following the steps outlined on the site, the application does not seem to do anything after I click the "apply and restart" button. It seems to stick at 'initializing' and does not restart even after waiting appox. 45min.
The second question I have is how do I graph an equation in this software. I'm new to Kepler and workflow softwares in general. I'm trying to apply this technology to help simulate a basic economy. However, I need to be able to graph a line, and have it follow some rules, here is an example : The user must choose a rule. ex. when y > 100; R1 would state divide by 50, R2 states subtract 98. x=2 (this is given by user) plug into y=2x. ' this compounds, so the result of 2*2 will equal x in the next iteration and 4*2 will equal x in the next etc... y > 100. when true, R1 or R2 will be invoked. The real time output will be graphed in Kepler, but the data at given time intervals
should be written to an Excel or CSV file with a time stamp (seconds from t=0) I've looked meticulously for tutorials for both this software and similar ones with no avail. Any help would be much appreciated. Thank you and happy holidays! Pranav
Updated by Matt Jones almost 14 years ago
The original reporter now reports that he got this to work by logging in as administrator before upgrading. He writes:
"The trouble with updating from 2.0 to 2.1 has been resolved. It was my fault, I simply forgot to run the program as an administrator and then update. The bugzilla report can be closed. It would be very helpful if you could please note this next to the directions for updating on the website."
However, didn't we have a feature where the user would be prompted for admin access when it was needed? Or was this only part of the installer? Either way, once the website instructions are updated to reflect the correct procedure, this bug can probably be closed without further action.
Updated by David Welker almost 14 years ago
Added documentation. This should not be a problem going forward, due to a change in how the module manager works.