Sponsored Content
Full Discussion: bc scale problem
Top Forums Shell Programming and Scripting bc scale problem Post 302556079 by cristalp on Friday 16th of September 2011 01:22:47 PM
Old 09-16-2011
bc scale problem

Dear Experts,

I want to use bc to do some multiplication and return me a value with number of decimal places defined by myself.

For example:
Code:
echo "scale=10; 1.65*7" | bc

returns me:
Code:
11.55

But what I really want is to have is a result with 10 digits after the point which should look like:
Code:
11.5500000000

But "scale" just doesn't work here. And, if I want to have result without decimal place, for 11.55, it should return me the result like:
Code:
12

Could I achieve these without the help of other command. I know I could pipe the result to awk or another bc (by division for which scale works), but I just interested in if a single bc with some special option can do it simply?

I would greatly appreciate to your kind help!

Last edited by cristalp; 09-16-2011 at 02:38 PM..
 

3 More Discussions You Might Find Interesting

1. Solaris

unable to allocate enough cells for gray scale

Hi, I tried to install a software (written in C) and run it on a sun machine. It is displaying the error: unable to allocate enough cells for gray scale. I closed all other apllications and set background to black to minimize usage of cells. But it is diaplaying the same error. Plz help... (1 Reply)
Discussion started by: raz
1 Replies

2. UNIX for Dummies Questions & Answers

Any company running large scale grid platform still

Hi buddy, I would like to know are there any company still running large scale grid platform like Parabon? Parabon is the only company running such kind of platform and purchasing CPU power. Is that right? Thanks, Colapig (0 Replies)
Discussion started by: colapig
0 Replies

3. Programming

Isosurface and a 2D figure with the same scale and origin using mayavi

I am using mayavi to plot an iso surface from a 3D array s using the following piece of code: src = mlab.pipeline.scalar_field(s) fig=mlab.pipeline.iso_surface(src, color=(1.0,0.0,0.0), contours=, opacity=0.3) mlab.pipeline.iso_surface(src, color=(0.0,1.0,1.0),contours=, opacity=0.3) Then... (0 Replies)
Discussion started by: jaldo0805
0 Replies
OD(1)								   User Commands							     OD(1)

NAME
od - dump files in octal and other formats SYNOPSIS
od [OPTION]... [FILE]... od [-abcdfilosx]... [FILE] [[+]OFFSET[.][b]] od --traditional [OPTION]... [FILE] [[+]OFFSET[.][b] [+][LABEL][.][b]] DESCRIPTION
Write an unambiguous representation, octal bytes by default, of FILE to standard output. With more than one FILE argument, concatenate them in the listed order to form the input. With no FILE, or when FILE is -, read standard input. If first and second call formats both apply, the second format is assumed if the last operand begins with + or (if there are 2 operands) a digit. An OFFSET operand means -j OFFSET. LABEL is the pseudo-address at first byte printed, incremented when dump is progressing. For OFFSET and LABEL, a 0x or 0X prefix indicates hexadecimal; suffixes may be . for octal and b for multiply by 512. Mandatory arguments to long options are mandatory for short options too. -A, --address-radix=RADIX output format for file offsets; RADIX is one of [doxn], for Decimal, Octal, Hex or None --endian={big|little} swap input bytes according the specified order -j, --skip-bytes=BYTES skip BYTES input bytes first -N, --read-bytes=BYTES limit dump to BYTES input bytes -S BYTES, --strings[=BYTES] output strings of at least BYTES graphic chars; 3 is implied when BYTES is not specified -t, --format=TYPE select output format or formats -v, --output-duplicates do not use * to mark line suppression -w[BYTES], --width[=BYTES] output BYTES bytes per output line; 32 is implied when BYTES is not specified --traditional accept arguments in third form above --help display this help and exit --version output version information and exit Traditional format specifications may be intermixed; they accumulate: -a same as -t a, select named characters, ignoring high-order bit -b same as -t o1, select octal bytes -c same as -t c, select printable characters or backslash escapes -d same as -t u2, select unsigned decimal 2-byte units -f same as -t fF, select floats -i same as -t dI, select decimal ints -l same as -t dL, select decimal longs -o same as -t o2, select octal 2-byte units -s same as -t d2, select decimal 2-byte units -x same as -t x2, select hexadecimal 2-byte units TYPE is made up of one or more of these specifications: a named character, ignoring high-order bit c printable character or backslash escape d[SIZE] signed decimal, SIZE bytes per integer f[SIZE] floating point, SIZE bytes per float o[SIZE] octal, SIZE bytes per integer u[SIZE] unsigned decimal, SIZE bytes per integer x[SIZE] hexadecimal, SIZE bytes per integer SIZE is a number. For TYPE in [doux], SIZE may also be C for sizeof(char), S for sizeof(short), I for sizeof(int) or L for sizeof(long). If TYPE is f, SIZE may also be F for sizeof(float), D for sizeof(double) or L for sizeof(long double). Adding a z suffix to any type displays printable characters at the end of each output line. BYTES is hex with 0x or 0X prefix, and may have a multiplier suffix: b 512 KB 1000 K 1024 MB 1000*1000 M 1024*1024 and so on for G, T, P, E, Z, Y. EXAMPLES
od -A x -t x1z -v Display hexdump format output od -A o -t oS -w16 The default output format used by od AUTHOR
Written by Jim Meyering. REPORTING BUGS
GNU coreutils online help: <http://www.gnu.org/software/coreutils/> Report od translation bugs to <http://translationproject.org/team/> COPYRIGHT
Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. SEE ALSO
Full documentation at: <http://www.gnu.org/software/coreutils/od> or available locally via: info '(coreutils) od invocation' GNU coreutils 8.28 January 2018 OD(1)
All times are GMT -4. The time now is 10:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy