Nabin K. Malakar, Ph.D.

NASA JPL
I am a computational physicist working on societal applications of machine-learning techniques.

Research Links

My research interests span multi-disciplinary fields involving Societal applications of Machine Learning, Decision-theoretic approach to automated Experimental Design, Bayesian statistical data analysis and signal processing.

Linkedin


Interested about the picture? Autonomous experimental design allows us to answer the question of where to take the measurements. More about it is here...

Hobbies

I addition to the research, I also like to hike, bike, read and play with water color.

Thanks for the visit. Please feel free to visit my Weblogs.

Welcome to nabinkm.com. Please visit again.

Showing posts with label code. Show all posts
Showing posts with label code. Show all posts

Friday, February 11, 2011

Coding Practice in MatLAB

MATLAB for Engineers (2nd Edition)I had a post trying to relate a good coding practice in Matlab to the bus resistance of the code.

This week, in mathworks blog,  Brett suggested three nice tutorials for matlab enthusiastic. This is equally useful to  experts as well. They are:


From:

Good MATLAB Coding Practices


Sunday, August 1, 2010

Bus Resistance of a Code or Program

Last year I was on a training for a operating computations on grid at Cornell. Our instructor from Texas threw a Joke: "Do you know the bus resistance of your code?"
Everyone was surprised to hear the question. The Joke is interesting because it indicates one thing and tells you something else. While some people were thinking of how the string of 1's and 0's that travel through the computer data bus might come across such bus resistance, he explained in a funny way.

Here we go:
Imagine one fine friday evening you are grabbing a beer and walking down the road, and you are hit by a bus. What happens to your code? The next day the project manager decides to give your code to your colleague to continue the project. If your code is not properly commented, he will be completely lost in there. 
So, the bus resistance is given by the amount of comments in a code and the readability of your code by someone else.
Let us wish that this happens to no one. However, for the continuity of the project in your lab, your code must have very high bus resistance value.
The moral is: comment your code as much as you can.
Beginning C++ Through Game Programming, Second EditionPython Programming: An Introduction to Computer Science 2nd EditionC Programming Language (2nd Edition)
Cheers!

Are your codes bus resistant?