Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connecting Dynamic Aspen Custom Modeler (ACM) with FOQUS #1044

Open
boverhof opened this issue Jul 12, 2022 · 2 comments
Open

Connecting Dynamic Aspen Custom Modeler (ACM) with FOQUS #1044

boverhof opened this issue Jul 12, 2022 · 2 comments
Assignees
Labels
Priority:Normal Normal Priority Issue or PR SimSinter Issues related to uploading and reading simulation files in SimSinter

Comments

@boverhof
Copy link
Member

boverhof commented Jul 12, 2022

Description

One of the main issues with running dynamic ACM models with FOQUS is the requirement to specify a ‘TimeSeries’ vector which determines how long the simulation will run for and when to record dynamic data. This is a problem when working with cycle models which may operate using event driven conditions or switching (ex: switching to desorption when so much CO2 is captured) and the total cycle time or time you need to simulate for isn’t known before starting the simulation.

Test 1:

A simpler version of a model to test this connection was developed using the BFB example model. The cycles are set up using ACM’s Task tool, and here a Task is used to just change the inlet gas flow rate and simulate until the CO2 capture reaches a certain value. From running the simulation in ACM, it is found that this takes 375 seconds for the model to achieve this capture and finish running. The first test is to just only set a single value in the ‘TimeSeries’ vector which is sufficiently larger than the time required from the task. In this test I just used 1000 seconds.

Screen Shot 2022-07-12 at 1 35 45 PM

When running this through FOQUS with the 1000 second time series entry, the simulation stops at 375 seconds (when the task completes) and FOQUS gives the ‘Run Completed Successfully’ message and everything reads fine. So, this method works for this smaller simulation, and it can be tested on the full cycle model.

The task tool in ACM is like a structure that sits over top of the simulation that can change boundary conditions within the model based on certain criteria (time, model variables, etc.). Now with this, there are tons of different ways to set these up. For test 1, I write one myself that activates after the model starts. It changes the flue gas flow rate and then will simply pause/finish the simulation when the capture reaches a certain value. This is really simple, only 5 lines of code total need to be written. The other tests use a task which has been used to simulate the entire temperature swing CO2 adsorption cycle. This still uses the ACM task tool but contains much more code (234 lines that is actually generated using an interface from ACM).

@boverhof
Copy link
Member Author

@Ryan-Hughes-8 can you provide the simulation files so I can attempt to run test1.

@boverhof boverhof moved this to In Progress in 2022 Sept Release Jul 12, 2022
@Ryan-Hughes-8
Copy link
Contributor

@boverhof this zip file contains the BFB ACM file, simsinter .json file, FOQUS file, and a word doc explaining how to create the test 1 task in ACM.

simple model.zip

@ksbeattie ksbeattie added the Priority:Normal Normal Priority Issue or PR label Jul 19, 2022
@ksbeattie ksbeattie moved this to In Progress in 2022 Dec Release Oct 4, 2022
@ksbeattie ksbeattie added the SimSinter Issues related to uploading and reading simulation files in SimSinter label Mar 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:Normal Normal Priority Issue or PR SimSinter Issues related to uploading and reading simulation files in SimSinter
Projects
None yet
Development

No branches or pull requests

3 participants