Friday, December 7, 2007

Hey Everyone!

This is exam time!
All i got to say is that stay focussed!
Everyone admires someone or desires something, but the question is what price can we pay for achieving him/her/it?

This is one time lets take inspiration and lets show ourselves our own best!

Always remember everyone of us is best of 2million, why not best of other few?
(you wanna know the logic of 2 million, ask me at avonvarun@yahoo.co.in)

Friday, November 2, 2007

CAT Finale!

Sometimes Winning Is Everything!

Yes, this is one point this famous Chak De Tagline holds true!

A lot is at stake with this and following examinations coming up. So, lets come up with a perfect and fool proof plan to make that percentile level go a little higher by efforts of the final days. Everyone follows his/her own plan, some people do not really follow a plan, instead, just go on. To such people, i have a question:

If you do not believe in planning and managing your work and time, then why do you think people will come up to you for management tasks? After all, thats what you are out to do!

So, here is one last week plan i feel will give you a self assessment on how you can attempt your CAT examination! So here it goes:

Step 1
Break up your last seven 24 hours.
Lets suppose you would like to sleep 8 hours a day and take 4hours of daily activities. So, you have 12 hours of study a day!

Step 2
Attempt 2 FLTs ( Full Length Tests) a day. Attempt the first one early in the morning after a brisk walk (so you stay active and full in concentration). Do not use a rough sheet, so you'll know which questions will let you save time. Ofcourse questions do not repeat, but the type does! Do not attempt questions you are not sure of. After having a bath and breakfast, analyse and solve the rest of the paper using solution key (if you have one) or through your study material.

Step 3
Attempt the next one with rough work. Again do not attempt any question you are not sure of. You'll be tempted to make lucky guesses, but try not to cheat yourself! Give yourself a break after this attempt and again analyse and solve the FLT. Note the timing and marks difference between first FLT and second FLT. You'll know your capabilities and strengths better. Also your sectional or question based timing will become clear.

Step 4
If there's more time, its upto you to decide. You may listen to motivating english or Chak De songs, or maybe have a look at your study material. Choice is yours.

Go for this process for 3 days, i.e., you have to attempt 6 FLTs during this period. Now, for the next 2 days, allow yourself to attempt questions you are not sure of. Try only smart guesses! Follow the same pattern of 1 FLT with rough work and 2nd without. On the sixth day, attempt these two FLTs with all kinds of guesses, lucky ones and smart ones. Dont just attempt it all.

Now the final day before CAT, just take a look at your 12 FLTs. Mark your best attempts, note which sections take up most of your time and thought process. Analyse which way you can give yourself most time in your actual CAT paper. Strategise your D-Day!

Your strategy for exam can be devised in two ways:
1. Attempt all the paper, section wise. Attempt the sections in your preferential order.
2. Attempt the paper to make sure you clear sectional cut-offs. This strategy involves quick attempt of all sections for obtaining the quick and confident score, and then attempting your best sections to make your result all better.

All the best. You can modify or chose your own plan as per your conveneince. But, if you do not structure your approach, you may lose out some important percentile levels you could have gained at the last moment.

If you stop to grow, you actually stop!
So keep going, each smartly used moment may give you an extra edge over others!

Realised And Corrected My Mistake!

The major mistake i committed was writing an amature abstract! So, i thought my main focus should be the representing my idea in most efficient and attractive way so readers should get an insight with my research through the Abstract!

So, i start to search for best way to write an abstract. Here's what i got!

How to Write an Abstract!
Abstract
Abstract is written after the report is completed, although it is intended to be read first.
Because on-line search databases typically contain only abstracts, it is vital to write a complete but concise description of your work to entice potential readers into obtaining a copy of the full paper. This article describes how to write a good computer architecture abstract for both conference and journal papers. Writers should follow a checklist consisting of: motivation, problem statement, approach, results, and conclusions. Following this checklist should increase the chance of people taking the time to obtain and read your complete paper.
Checklist: Parts of an Abstract
Despite the fact that an abstract is quite brief, it must do almost as much work as the multi-page paper that follows it. In a computer architecture paper, this means that it should in most cases include the following sections. Each section is typically a single sentence, although there is room for creativity. In particular, the parts may be merged or spread among a set of sentences. Use the following as a checklist for your next abstract:
Motivation:Why do we care about the problem and the results? If the problem isn't obviously "interesting" it might be better to put motivation first; but if your work is incremental progress on a problem that is widely recognized as important, then it is probably better to put the problem statement first to indicate which piece of the larger problem you are breaking off to work on. This section should include the importance of your work, the difficulty of the area, and the impact it might have if successful.
Problem statement:What problem are you trying to solve? What is the scope of your work (a generalized approach, or for a specific situation)? Be careful not to use too much jargon. In some cases it is appropriate to put the problem statement before the motivation, but usually this only works if most readers already understand why the problem is important.
Approach:How did you go about solving or making progress on the problem? Did you use simulation, analytic models, prototype construction, or analysis of field data for an actual product? What was the extent of your work (did you look at one application program or a hundred programs in twenty different programming languages?) What important variables did you control, ignore, or measure?
Results:What's the answer? Specifically, most good computer architecture papers conclude that something is so many percent faster, cheaper, smaller, or otherwise better than something else. Put the result there, in numbers. Avoid vague, hand-waving results such as "very", "small", or "significant." If you must be vague, you are only given license to do so when you can talk about orders-of-magnitude improvement. There is a tension here in that you should not provide numbers that can be easily misinterpreted, but on the other hand you don't have room for all the caveats.
Conclusions:What are the implications of your answer? Is it going to change the world (unlikely), be a significant "win", be a nice hack, or simply serve as a road sign indicating that this path is a waste of time (all of the previous results are useful). Are your results general, potentially generalizable, or specific to a particular case?
Other Considerations
An abstract must be a fully self-contained, capsule description of the paper. It can't assume (or attempt to provoke) the reader into flipping through looking for an explanation of what is meant by some vague statement. It must make sense all by itself. Some points to consider include:
  • Meet the word count limitation
  • Any major restrictions or limitations on the results should be stated, if only by using "weasel-words" such as "might", "could", "may", and "seem".
  • Some publications request "keywords". These have two purposes. They are used to facilitate keyword index searches, which are greatly reduced in importance now that on-line abstract text searching is commonly used. However, they are also used to assign papers to review committees or editors, which can be extremely important to your fate. So make sure that the keywords you pick make assigning your paper to a review category obvious (for example, if there is a list of conference topics, use your chosen topic area as one of the keyword tuples). Be sure that those exact phrases appear in your abstract, so that they will turn up at the top of a search result listing.
  • Do not include a statement of scope; a sentence like "this paper will look at...." is inappropriate in an informative abstract.
  • Revise the draft into smooth, stand-alone prose; the abstract itself should be a mini-essay.
  • Edit the revision. Be sure that the abstract is complete and accurate. Double check that the abstract is written in the same voice as is the paper.
Writing an efficient abstract is hard work, but will repay you with increased impact on the world by enticing people to read your publications. Make sure that all the components of a good abstract are included in the next one you write.

Friday, October 12, 2007

Aim Of The Blog!

The basic aim of this blog is to step by step highlight the progress and modification in the minor project.
You get to learn from each stage, and thats what this blog shows for me.
Though the blog is starting from the third phase of the progress, better late than never!

An Idea Rejected!

As the world moves on to next level of technology, computers and machines need to become more interactive and intelligent. The problem domains have gone so vast that explicit description for each considerable case makes it highly difficult and error prone technique for programming. Therefore, the solution may not be achieved by Case Based Reasoning (CBR). The solution is given by concepts of artificial intelligence. Though intelligence is not very clearly defined, still programs may be given a status of somewhat intelligent or highly intelligent depending upon the behavioral outputs that they give according to the problem domains.

The major objective is to conceptualize the real estate cost estimations using the artificial intelligence concepts. Major concepts to be used fall under the category of Neural Networks, Fuzzy Logic and Genetic Programming. The real estate cost estimation possesses a challenge that there are various parameters that drive the markets which do not have specified metric for evaluation. But still the human agents are able to quote the prices by examining those parameters. They may not even know how they are able to give variable weightage to different parameters, it may be concluded that they do so by their experience. Thus the program needs certain level of intelligence to make accurate or nearly accurate estimations.

Such a system would essentially need Fuzzy Logic implementation since the parameters defining the domain are otherwise not determinable. Only relative relations may be determined using membership values.

Though for estimation to be automatically or intelligently determined, either or both neural networks and genetic algorithms can be used. Neural networks provide computing and learning capability through the proposed model of Multi-Layered Perceptron with Backpropogation whereas genetic algorithms provide the concept of Fitness Function to improvise upon the results. More techniques from one or both concepts may be used for implementation.

The scope of this paper is limited to conceptualization and development of algorithms for providing solution to the problem domain by means of supervised learning in neural network model and improvisation of result by fitness function concept of genetic algorithms which may be extended to complete implementation further.