iMechanica - C++ - Comments

How should I apply for this

Lin Ma — Thu, 25 Sep 2008 20:05:50 -0400

How should I apply for this position? Thanks.

MPM

Nguyen Chau Linh — Tue, 18 Mar 2008 23:33:17 -0400

Prof. Nain and his co-worker are research on Material Point Method, you can search on Google with keywords: Nairn, MPM, crack propagation...

Fun,

MPM + rockfall

pedroso — Tue, 18 Mar 2008 19:54:29 -0400

Hi, that's interesting. We, including Dr. Anna Giacomini, are also planning to run some simulations of rockfalls using the (Generalized)MPM.

MPM

Michael G. Sakellariou — Tue, 18 Mar 2008 07:19:00 -0400

We are developing a 3-D rockfall simulation in a GIS environment and we think the MPM could be very powerful method in simulating the impact phenomenon.

Library for design patterns/idioms

N. Sukumar — Sat, 19 Jan 2008 00:41:09 -0500

Good luck, Biswajit. A C++ library that contains implementations of design patterns and idioms is Loki.

Dear Biswajit, Wish you

Teng Li — Fri, 18 Jan 2008 10:25:43 -0500

Dear Biswajit,

Wish you the best in your new post, and we look forward to your coming back to iMechanica.

-Teng

C++ Idioms and Design Patterns...

Ajit R. Jadhav — Thu, 17 Jan 2008 22:59:28 -0500

Dear Biswajit,

Good that you broached this topic up... I was wondering if discussions related to programming would be appropriate here at iMechanica---especially, discussions at a somewhat more abstract level (i.e. not concerned with the syntax of languages etc.)... Also, the more serious amongst tutorial codes in C++... I was already wondering if I should be posting some of my code my general blog site... So, I was really delighted to see your above post here...

About C++ idioms. A very closely related topic is Design Patterns. For example, see here and here.

With that said, I have a word of caution, though. IMO it is best *NOT* to try to use design patterns right in the first iteration of a major version of your software--v 1.0 or v 2.0 or whatever....

I know I am sounding like an unenthusiastic fool who has no respect whatsoever for the abstract or high-level design here... But the way I loook at it, there has been sometimes too much of a good thing w.r.t. the high-level abstract design too... Just for example, notice that issues and factors such as data locality (cache and virtual memory), ease of IPC and of parallelization, etc. ought to enter software design... Yet, as a matter of fact, a lot of issues of this nature cannot become as clear as they should be, until the first cut is already over. (We don't have to wait until the profiling stage, but at least a major chunk of the code ought to first exist before people can really get such parts right.) Hence, it is sometimes better to go ahead with a simple scheme involving a minimal number of very loosely coupled classes, and then put them all together into a better framework... A real bottom-up design exercise, in a sense....

Of course, my above comment does not apply to your above post of C++ idioms (or your example of the Factory idiom)... I just wanted to qualify my recommendation of design patterns, that's all...

-----

Biswajit, on a personal note: If you want to quit USA, that's good (ask me why (!)) but you don't want to therefore return to India, do you?

One way or the other, I enjoyed your answers over a range of issues here... Let me wish you the very best in your new environment, and, as Zhigang said, do let us know once you are ready to chat here at iMechanica again... I look forward to interacting with you soon again...

--Ajit

Best wishes for Biswajit

Zhigang Suo — Thu, 17 Jan 2008 21:07:33 -0500

Dear Biswajit: Thank you so much for your contributions to iMechanica. I have learned much from you. Please let us know when you are settled in your new environment. Good Luck and best wishes, Zhigang