Backwards Compatibility

Chris_DSMC · June 15, 2015, 06:42

Hello Community,

I am currently working on the DSMC-Solver in OpenFOAM. I already made some changes in the code and implemented a new boundary condition. Because I am planing some new features for the Solver, I think there will be some more modifications. Of course we are planing to contribute our changes to the official release of OpenFOAM after our project (if they are interested

)

I am wondering how important backwards compatibility is to the community?

To give an example: Like I said, I added a new boundary condition. Because of this I added a new boundaryField called "boundaryRhoN". The existing boundary condition "freeStream" specifies the number density in the "dsmcProperties" file. Now this is a bit contrary to the new boundaryCondition. Now three ways come to my mint:

1) I implement everything clean and let freeStream also use the boundaryRhoN file. In this way it would not be possible to use older Models with my version. (Of course I would update the tutorials)

or

2) I make sure, that it is possible to run the existing tutorials with my version, which of course could be a bit more creepy in the code.

or

3) I completly do not touch the existing boundary condition. (Which I think is no option, because it would lead to double code and would break some other basic rules using object oriented programming with c++)

I am very curious to your answers

Best regards

Chris_DSMC · June 17, 2015, 14:09

Hi there,

do I have to make myself a bit more clear?
If anybody has a hint, for example something I missed in the programmers guide, I would be very grateful.

The question is, if it is allowed to change the user interface of a solver such, that older models are not runable with my version any more.

I am happy for every answer.

Wish you all a nice day.

June 15, 2015, 06:42	Backwards Compatibility	#1
Chris_DSMC New Member Join Date: Jun 2014 Posts: 9 Rep Power: 11	Hello Community, I am currently working on the DSMC-Solver in OpenFOAM. I already made some changes in the code and implemented a new boundary condition. Because I am planing some new features for the Solver, I think there will be some more modifications. Of course we are planing to contribute our changes to the official release of OpenFOAM after our project (if they are interested ) I am wondering how important backwards compatibility is to the community? To give an example: Like I said, I added a new boundary condition. Because of this I added a new boundaryField called "boundaryRhoN". The existing boundary condition "freeStream" specifies the number density in the "dsmcProperties" file. Now this is a bit contrary to the new boundaryCondition. Now three ways come to my mint: 1) I implement everything clean and let freeStream also use the boundaryRhoN file. In this way it would not be possible to use older Models with my version. (Of course I would update the tutorials) or 2) I make sure, that it is possible to run the existing tutorials with my version, which of course could be a bit more creepy in the code. or 3) I completly do not touch the existing boundary condition. (Which I think is no option, because it would lead to double code and would break some other basic rules using object oriented programming with c++) I am very curious to your answers Best regards

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
convert .msh to .stl and backwards	Lilly	ANSYS Meshing & Geometry	2	October 22, 2017 20:03
Version Compatibility	vish	STAR-CCM+	1	March 19, 2014 14:16
Compatibility of FLUENT & Hypermesh	preshitupadhye	FLUENT	0	October 27, 2010 11:47
data compatibility	Shuo	Main CFD Forum	0	November 20, 2008 22:48
Backwards compatibility of Fluent 6.3 with 6.2	Brian	FLUENT	1	April 4, 2007 21:52

June 17, 2015, 14:09		#2
Chris_DSMC New Member Join Date: Jun 2014 Posts: 9 Rep Power: 11	Hi there, do I have to make myself a bit more clear? If anybody has a hint, for example something I missed in the programmers guide, I would be very grateful. The question is, if it is allowed to change the user interface of a solver such, that older models are not runable with my version any more. I am happy for every answer. Wish you all a nice day.