{"id":68521,"date":"2025-09-11T10:02:10","date_gmt":"2025-09-11T14:02:10","guid":{"rendered":"https:\/\/blogs.sw.siemens.com\/simcenter\/?p=68521"},"modified":"2026-03-26T06:48:54","modified_gmt":"2026-03-26T10:48:54","slug":"the-merge-men","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/simcenter\/the-merge-men\/","title":{"rendered":"The Merge Men: A Simcenter Amesim Tale"},"content":{"rendered":"\n

From Integration Nightmares to Three-way Merge Magic<\/h2>\n\n\n\n
<\/div>\n\n\n\n
\n

Today’s the day. <\/p>\n<\/blockquote>\n\n\n\n

Weeks of intense work on Simcenter Amesim<\/a> models culminate here. Two teams of simulation engineers \u2013 the electric drive (Peggy and Sal) and passenger comfort (Ken and Pete) teams \u2013 have been hard at work to reach performance goals. Now is the time for their work to be merged, and for the air conditioning system designed by our PASCOM whizzes to be integrated into the overall model. That\u2019s where I come in \u2013 I\u2019m tasked with combining the work of both teams into one final model.<\/p>\n\n\n\n

\n
<\/div>\n\n\n\n
\n
It's 9:15 AM, I'm locked in for what I know will be an intense day. The familiar bong of my email client announces the arrival of a new message \u2013 could this be it? Palms slightly damp, I alt-tab to the client and mouse over the message. <\/em>

Subject: RE: RE: FW: AirCon Loop model for integration<\/em><\/code>
<\/kbd>
This is starting well, looks like it's passed through a few pairs of hands already...<\/em> 
Ugh. A file attachment: <\/em>

EVDrivetrain_ACLoop_forIntegration_attempt2_v3_final.piz<\/em>
<\/kbd>
So many iterations. An extension rename to hoodwink the email client? A bead of sweat forms at the back of my head and starts making its way down my spine.<\/em>
I start reading the email, then skip to the interesting bit:<\/em>

\u201cAll you have to do is:\u201d [...] 
<\/kbd>
followed by a thousand intricate and easy-to-fudge changes to make to the combined model. What the...<\/em>
In a frenzy, I read down the list and reach the last item: <\/em>

\u201cSay a quick prayer because combining these models rarely goes as expected at the first attempt. Good luck!\u201d<\/kbd>

How did we get here? Is this really how this has to be? I feel trapped. It gets harder to breathe as I start getting overwhelmed by the difficulty of what I'm about to attempt...<\/em><\/pre>\n<\/div>\n\n\n\n
<\/div>\n<\/div>\n\n\n
\n
\"The<\/a><\/figure><\/div>\n\n\n
…GASP! I wake up, drenched in a cold sweat. I grab my phone off my bedside table – it’s 5:47 AM, integration day. Deep calming breaths slow my heart down \u2013 it was just a nightmare. With 45 minutes to go before the day starts, I fall back asleep, with the quiet hope that things are going to go well today.<\/p>\n\n\n\n
<\/div>\n\n\n\n
\n
9:15 AM – Integration Day at the Agency<\/p>\n<\/blockquote>\n\n\n\n
I’m locked in for what I know will be an intense day. A freshly brewed coffee sits in front of me \u2013 but no email chimes come this time. I go straight to Simcenter Amesim and open up Simcenter Client for Git<\/a>. I have a game plan for today.
You see, the nightmare I had this morning wasn’t just a nightmare, it’s an echo of the past. A past I’m glad I\u2019ve left behind.
This time around, we started versioning everything in System Simulation Client for Git, and used the same model as a basis for both teams\u2019 work. We then split the activities into two branches, focused on their own goals and with their own constraints.
Each of the teams has worked on its own version of the model, with System Simulation Client for Git’s role-based access management feature. We have been able to independently work on models, data files and user libraries, since Client for Git automatically manages these dependencies for us. This has given us freedom to make big changes without fear of stepping on other departments\u2019 toes.
The key to us being able to collaborate effectively together lies in how everything can come together in the end. Both the Passenger Comfort department’s model and that of my fellow electric drive systems colleagues\u2019 have changed quite significantly from that shared initial point. Let’s see how System Simulation Client for Git can handle this historically messy bit of model integration…
<\/p>\n\n\n\n
Just as I have this thought pinging through my mind, my colleague Roger rushes in, clearly panicked.<\/p>\n\n\n\n
\n
<\/div>\n\n\n\n
\n
\u201cWhich version of Simcenter Amesim are the drivetrain folks running??\u201d<\/em><\/pre>\n\n\n\n
\u201cLet me see... It's Simcenter Amesim 2504 - why?\u201d<\/em><\/pre>\n<\/div>\n\n\n\n
<\/div>\n<\/div>\n\n\n\n
Rogers’s shoulders relax, and a slow happy smile spreads across his face.<\/p>\n\n\n\n
\n
<\/div>\n\n\n\n
\n
\u201cDid you hear about the new-\u201d<\/em><\/pre>\n\n\n\n
\u201cYep, I just finished checking out this nice blog post about it!\u201d<\/em><\/pre>\n\n\n\n
\u201cYeah, looks pretty promising. Go ahead with the merge then, let me know if you need help!\u201d<\/em><\/pre>\n<\/div>\n\n\n\n
<\/div>\n<\/div>\n\n\n\n
Roger ambles out, clearly showing scars of a similar past experience to mine. I guess sooner or later we all become hardened veterans when it comes to collaborating on complex projects.<\/p>\n\n\n\n
<\/div>\n\n\n\n
\n
9:45 AM – The Version History<\/p>\n<\/blockquote>\n\n\n\n
Coffee in hand, I open my own model in Simcenter Amesim. Since it is managed in System Simulation Client for Git, I automatically get a bird\u2019s-eye view of the history of my model collection.<\/p>\n\n\n\n
First on the list is to go through my collection\u2019s version history and ensure that my model is ready to be merged.<\/p>\n\n\n
\n
\"\"<\/a>
Both teams have been very busy, advancing their Electrical Vehicle simulation models in separate branches, responding to new needs and challenges<\/figcaption><\/figure><\/div>\n\n\n
My versioning comments seem in order, but I know Simcenter Amesim 2504<\/a> has a couple of tricks up its sleeve. I multiple-select my latest and initial versions, and right click \u2013 there it is: the new Model Comparison baked right into Simcenter Amesim, and fully integrated into System Simulation Client for Git.<\/p>\n\n\n\n
Sal compares his work with earlier iterations made by his colleague Peggy, early on in the design process.<\/figcaption><\/figure>\n\n\n\n
The nifty new sketch preview in Simcenter Amesim 2504 helps me keep my finger on the pulse of all the differences \u2013 I click a difference, and up pops the component it corresponds to. The days of manually cross-referencing parameter values and component names are left behind me in the dust. <\/p>\n\n\n\n
I\u2019m in the zone now, running down the checklist of changes between the two models, to make sure that the work we\u2019ve all been doing can finally be merged.<\/p>\n\n\n\n
I can\u2019t miss a single thing here \u2013 every single connection, submodel and parameter value needs to be just right, otherwise I might really be in trouble once I try to combine the two models. Thankfully, Model Comparison allows me to dive deep into the detail, so I have control of everything.<\/p>\n\n\n\n
<\/div>\n\n\n\n
\n
10:15 AM – The Comparison<\/p>\n<\/blockquote>\n\n\n\n
Okay, final checks done. It\u2019s time to finally do this. My old copy\/paste\/pray techniques long abandoned, I go back to the version history for this collection. Luckily, it also shows me the evolutions that my e-Drive colleagues have been working on.<\/p>\n\n\n\n
\n
\n
My friend Peggy from the EV drivetrain department has just informed me that the final checks on her side are a go as well \u2013 the time has come: I pull up the contextual menu for the model with the thermal cooling loop and click \u201cMerge from\u201d.<\/p>\n\n\n\n
Tense seconds go by while System Simulation Client for Git attempts an automatic merge \u2013 if we are extremely lucky, the changes I\u2019ve made to the model are to different parts compared to Peggy\u2019s model. Let\u2019s not kid ourselves though\u2026<\/p>\n\n\n\n
Sure enough, System Simulation Client for Git dutifully tells me that my collection is in a state of conflict, and I\u2019m prepared: I pull out my fine model-versioning scalpel and open Three-way Merge to manual resolve the merge conflicts.<\/p>\n\n\n\n
Slightly overwhelmed with the sheer amount of difference rows, I quickly get the hang of this thing: Three-way Merge is showing me a simultaneous comparison between the latest versions of both e-Drive and AC loop models, and the initial model which both projects are based on.<\/p>\n<\/div>\n\n\n\n
\n
\"\"<\/a>
Both design branches are ready to be merged into a single integrated model<\/figcaption><\/figure><\/div><\/div>\n<\/div>\n\n\n\n
Now it\u2019s just a matter of picking and choosing \u2013 every single conflict where Peggy and Ken’s teams have both made concurrent changes to the model is a decision to be made. I can easily see where our modeling assumptions have differed, and how that affects the structure and parameterization of our models.<\/p>\n\n\n\n
Merging the models goes by in a breeze: conflicts are highlighted, choices are clear, and the models will be merged into their final state automatically by Three-way Merge<\/figcaption><\/figure>\n\n\n\n
Since I oversee the final integration, things are flowing, not a hitch in sight. I hop on a quick call with Sal and Pete at one point, since I was stumped by one of the conflicts, and we were able to quickly make the right choice \u2013 both teams messed up a parameter value, and should have left it as it was initially set. With the right choice settled, the change is as easy as a simple button press.<\/p>\n\n\n\n
<\/div>\n\n\n\n
\n
10:55 AM – The Resolution<\/p>\n<\/blockquote>\n\n\n\n
I reach the bottom of the conflict list \u2013 I\u2019ve made a choice for every single item, and I haven\u2019t even broken a sweat.<\/p>\n\n\n\n
\n
\n
My experience of past troubles rears its head one last time just as I\u2019m about to click \u201cSave and quit\u201d to finalize the merge \u2013 but it\u2019s gone as quickly as it came. Once that\u2019s done, my model in Simcenter Amesim is refreshed with all the changes I\u2019ve made.<\/p>\n\n\n\n
I quickly go through it, making tweaks to connections and ensuring that everything is as I had set it. It all looks good.<\/p>\n\n\n\n
My work here is done. Or as Don would say: “Get out of here and move forward. This never happened. It will shock you how much it never happened”<\/p>\n<\/div>\n\n\n\n
\n
\"\"<\/a><\/figure><\/div><\/div>\n<\/div>\n\n\n\n
That beautiful moment has arrived: Resolve conflict -> mark as resolved \u00e1\u00e1\u00e1\u00e1nd upload.<\/p>\n\n\n\n
<\/div>\n\n\n\n
\n
11:00 AM – This Is My Moment<\/p>\n<\/blockquote>\n\n\n\n
Job done. And to think that this would have taken me multiple days in the past. HA!<\/p>\n\n\n
\n
\"Merge<\/a>
Who\u2019s up for a mid-morning drink<\/s> snack?<\/figcaption><\/figure><\/div>\n\n\n
[As our hero walks to his office door he abruptly turns and looks straight into the camera]: Next time you\u2019re faced with a model-merging nightmare in your collaborative projects with Simcenter Amesim, remember: with the right tools, integrating systems models is less like bomb-defusal and more like… snapping together bricks – modular, intuitive, and oddly satisfying.<\/p>\n\n\n\n
This feature is part of the Simcenter Amesim 2504 release:<\/p>\n\n\n\n
\n
Read release blog<\/a><\/div>\n<\/div>\n\n\n\n
\n
Try Simcenter Amesim<\/a><\/div>\n<\/div>\n\n\n\n
<\/div>\n\n\n\n\"Read<\/a>