Here's a screenshot of our latest OpenSees Cloud workspace. Input, documentation, output, and model viewer in one browser window! #OpenSees#OpenSeesCloud
Here's a screenshot of our latest OpenSees Cloud workspace. Input, documentation, output, and model viewer in one browser window! #OpenSees#OpenSeesCloud
We are getting close to launch after switching our #OpenSees back-end computing from Lambda functions to EC2 instances. Read more in our latest blog post.
https://t.co/POB1qovgqI
@Lissette_J1 Hello @Lissette_J1, it will be ready before you finish your Ph.D.😀 We're working on the model viewer right now along with the cloud computing architecture with #OpenSeesPy. We'll make a new blog post soon to give more details.
@najafilog@mikusscott Yes, we will offer services that do not require using the web browser as a front end for building an #OpenSees model to be analyzed in the cloud.
We have a new blog post describing how RAM will be utilized to its fullest potential on #OpenSeesCloud. Subscribe for updates and notifications on our next round of testing!
https://t.co/1xOsDYnS6p
We have been hard at work updating the #OpenSeesCloud back end, but took a break to write a new blog post, "Our License to Cloud"
https://t.co/xTYdmQKSbs
Our first round of beta testing for #OpenSeesCloud starts this Wednesday, December 8. If you signed up as a beta tester, you should have received an e-mail last Friday to opt-in for this round. 48 people have opted-in so far!
Beta testing for #OpenSees Cloud begins on December 6. Sign up by November 30 if you would like to participate in the first round.
https://t.co/BR8QYaEWqM
Are you curious about #serverless computing and what it means for #OpenSees? If so, check out this new blog post from OpenSees Cloud.
https://t.co/Xx05fsiuAW
Screen shot of the #OpenSeesCloud workspace. Input, model viewer, model information, and analysis time all in one web browser window. Beta testing starts soon. Sign up today at https://t.co/BR8QYaEWqM
@Alejoduarte23 Good question! In the cloud, we can monitor for memory leaks and implementation inefficiencies and bottlenecks in the core OpenSees, without exposing personal information or details of users' models.