Ever wondered how MSP for crops is calculated ?

Below is an attempt to present a simplified view, followed by some pertinent questions (just to have better understanding, not taking sides)&

The MSP is usually based on the recommendations by the Commission for Agricultural Costs and Prices (CACP

This estimation is usually done based on three types of calculation methods. These are A2 method, A2+FL method and C2 method.
As per the A2 method, MSP is set 50% higher than the amount farmer spends on farming including spending on seeds, fertilisers, pesticides, and labour.
C2 method includes A2 factors + economic value of the efforts of family members working on the farm + the value of other spending including rent and other assets. After calculating these, MSP is set at 50% above the derived amount.
A2+FL method is middle ground between the other methods were the MSP is set 50% higher than the amount that derives the amount farmer spend on farming on seeds, fertilisers, pesticides, and labour and the value of labour provided by the family members for agriculture.
The present MSP has been calculated based on the A2+FL method
Now some questions ...

With such varied geography, which requires different inputs, labour, methods... and hence different costs of growing same crop, how do you define a single MSP for a crop across nation ?
MSP without quality attached to it cannot be transacted in market. How do you go about ‘freshness’ of vegetables?
How do we go about ‘oil content’ in peanut 🥜 which often dictates prices by bulk commodity purchases. ?
How does government go about procuring ALL crop at MSP where crop production is in huge surplus (more than we need). Note that we have ~ 95 million tonnes of grain rotting in FCI

More from Farmer protest

You May Also Like

THREAD: 12 Things Everyone Should Know About IQ

1. IQ is one of the most heritable psychological traits – that is, individual differences in IQ are strongly associated with individual differences in genes (at least in fairly typical modern environments). https://t.co/3XxzW9bxLE


2. The heritability of IQ *increases* from childhood to adulthood. Meanwhile, the effect of the shared environment largely fades away. In other words, when it comes to IQ, nature becomes more important as we get older, nurture less.
https://t.co/UqtS1lpw3n


3. IQ scores have been increasing for the last century or so, a phenomenon known as the Flynn effect. https://t.co/sCZvCst3hw (N ≈ 4 million)

(Note that the Flynn effect shows that IQ isn't 100% genetic; it doesn't show that it's 100% environmental.)


4. IQ predicts many important real world outcomes.

For example, though far from perfect, IQ is the single-best predictor of job performance we have – much better than Emotional Intelligence, the Big Five, Grit, etc. https://t.co/rKUgKDAAVx https://t.co/DWbVI8QSU3


5. Higher IQ is associated with a lower risk of death from most causes, including cardiovascular disease, respiratory disease, most forms of cancer, homicide, suicide, and accident. https://t.co/PJjGNyeQRA (N = 728,160)
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.