openerp-india team mailing list archive

["Nhomar Hernandez \(Vauxoo\)" <nhomar@xxxxxxxxx>]

Public bug reported:

I saw this:

'factor_inv': fields.function(_factor_inv, digits_compute=dp.get_    precision('Product UoM'),
             fnct_inv=_factor_inv_write,
             method=True, string='Ratio',
             help='How many times this UoM is bigger than the reference Uo    M in this category:\n'\
                     '1 * (this unit) = ratio * (reference unit)', require    d=True),

When you verify the compute:

     def _compute_factor_inv(self, factor):
         return factor and round(1.0 / factor, 6) or 0.0


In what parallel world you save a FACTOR calculating with a rounding that provoce an bigger error than the solved for it.

If you look in a book, you can see how the indirect measure is un
precise and bad done, you need to measure directly and put results
exactly on your equations.

This algorith in moy point of view is totally wrong.

Example case.


Put a unit PCE.
Create anothe one where this unit is base, and bigger than base.
Put 12000

See how value is wrong calculated (and it must not be calculated.)


result.: Customer really unconfortable because he think system has really bad features in base.

Thanks.

** Affects: openobject-addons
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/932390

Title:
  [6.0 TRUNK] product Why factor_inv is calculated issue rounding

Status in OpenERP Addons (modules):
  New

Bug description:
  I saw this:

  'factor_inv': fields.function(_factor_inv, digits_compute=dp.get_    precision('Product UoM'),
               fnct_inv=_factor_inv_write,
               method=True, string='Ratio',
               help='How many times this UoM is bigger than the reference Uo    M in this category:\n'\
                       '1 * (this unit) = ratio * (reference unit)', require    d=True),

  When you verify the compute:

       def _compute_factor_inv(self, factor):
           return factor and round(1.0 / factor, 6) or 0.0

  
  In what parallel world you save a FACTOR calculating with a rounding that provoce an bigger error than the solved for it.

  If you look in a book, you can see how the indirect measure is un
  precise and bad done, you need to measure directly and put results
  exactly on your equations.

  This algorith in moy point of view is totally wrong.

  Example case.

  
  Put a unit PCE.
  Create anothe one where this unit is base, and bigger than base.
  Put 12000

  See how value is wrong calculated (and it must not be calculated.)

  
  result.: Customer really unconfortable because he think system has really bad features in base.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/932390/+subscriptions