Your Question is lacking key details.

For example, you have not shown explicitly how f and fproc were constructed. There is no code in your original Question like, say, a call to any export of the Interpolate package. You mention "an interpolation object, f(x)" but did not show or clearly describe what you did to create that. There are several ways to do such things in Maple, with several different commands from several different packages. You might be using commands from the CurveFitting, Statistics, or ArrayTools packages.

Also, your Question did not originally contain a sentence like, "The name "fproc" is not something I have in my  code, just the name, "f"." You may have edited your Question, and added that, since I first replied.

Quite a bit of what else you've written makes little to no sense without context. Even a clear sentence that stated that you were trying to perform numeric integration using an object returned by command X from the Interpolate package (where X is an actual command name). would have been useful and more clear. The word "object" can be used as a technical Maple term (jargon) or as a general English word, and without your mentioning the Interpolate package it becomes a matter of guessing here.

Why haven't you bothered to upload and attach a worksheet so that we could see what you have actually done, what Maple version you're using, with code to reproduce the problems? (Green up-arrow in the Mapleprimes editor)

@WA573 You can use any valid value that you want for the pointplot3d command's symbol, symbolsize, and color options.

p3dopt2.mw

@Ronan It's slightly bewildering, because I already mentioned using LibraryTools in your previous Question thread.

Saving/exporting your procedures from a worksheet to external files is a methodology that you yourself described, and was not proposed by responders to recent Question threads. It's not necessary.

Personally I think that authoring source in directly plaintext files has benefits, that especially manifest themselves if it's used and re-used over the years. But authoring in the GUI and then saving to external files is a backwards and unnecessary process.

@Ronan In this latest scenario (saving as .m format) there's no reason to even export/save at all.

In that situation you could just as easily use LibraryTools to Save the procedure or module directly to a .mla archive file.

See my earlier Reply above, for various benefits of having/authoring your code in plaintext files. Using the mint Maple syntax checker (at full strength, not the less flexible/weakened maplemint or CodeEdit/Startup facilities in the GUI) is yet another motivation.

I'm not the only person who sees benefits to using plaintext files for packages/procedures that you might utilize into the future; see also here for a comment by someone else in a related and recent discussion thread.

If none of that rationale interests you then you don't need to export/save your procedures/modules to external source files.

@nmacsai It wasn't clear to me from your original Question whether you wanted just the number of base b digits, or the actual conversion as well.

I guessed that it was just the number of base b digits.

@Carl Love I was shooting for speed, especially as n gets very large.

Are the numbers you want to handle only positive integers? Or floats?

How large are the numbers you want to handle?

How many number do you want to handle? How fast do you need it?

@Carl Love I've submitted a bug report.

@MAXR How's this?

I made a small correction to make the "dummy" curves reside along y=miny the smallest y-data value. By "dummy" curves I mean the seq of plot calls (of zero length) whose purpose is merely to introduce the corresponding legend items.

I used Maple 17.02.

Download MAXRcontourplot_acM17.mw

@Carl Love Have you submitted a bug report against save? If not then I will. I notice the same issue using fprintf with its "%P" format to handle a procedure.

It might be possible to continue to save as plaintext source using a workaround such as,

    Row := proc() local R:=`<|>`; R(args); end proc:

@MAXR Is this the coloring you want for the upper surface? It required only a very simple edit of the green component ("G" in "RGB"), using the previous worksheet's formulas.

If you plot that formula,
   plot3d(F(a,b)/(2-0.5)-0.333, a=0.1 .. 0.5, b=0.1 .. 0.5)
then you would see that it ranges from approximately 0 to 1, vertically. Thus I can easily use it in Red/Green/Blue RGB component formulas to get linear gradients.

>  restart; >  kernelopts(version); (1) >  with(plots): with(plottools): >  x:=[0.1, 0.2, 0.3, 0.4, 0.5, 0.1, 0.2, 0.3, 0.4, 0.5,     0.1, 0.2, 0.3, 0.4, 0.5,0.1, 0.2, 0.3, 0.4, 0.5,     0.1, 0.2, 0.3, 0.4, 0.5]: >  y:=[0.1, 0.1, 0.1, 0.1, 0.1, 0.2, 0.2, 0.2, 0.2, 0.2,     0.3, 0.3, 0.3, 0.3, 0.3, 0.4, 0.4, 0.4, 0.4, 0.4,     0.5,0.5,0.5,0.5,0.5]: >  z:=[1.971284960, 1.642401616, 1.372353338,1.153620572,0.9762759982, >      1.675502483, 1.411976881, 1.190627373,1.007730234,0.8570007139, >      1.397140245, 1.184230644, 1.003688984,0.852696223,0.7268039317, >      1.144791107, 0.9725020383,0.8257592921,0.7020549659,0.5979974836,                                                        0.9208492326, 0.7816302394, 0.6627749172,0.5620029444,0.4766238930]: >  M := Matrix(5,5,z)^%T: >  xydat := [<[0.1,0.2,0.3,0.4,0.5]>,<[0.1,0.2,0.3,0.4,0.5]>]: >  F := proc(a,b) option remember;    if not [a,b]::list(numeric) then return 'procname'(args); end if;    CurveFitting:-ArrayInterpolation(xydat, M,                                     Array(1..1, 1..1, 1..2,                                           [[[a,b]]]))[1,1]; end proc: >  P3 := plot3d(F(a,b), a=0.1 .. 0.5, b=0.1 .. 0.5,              color=[F(a,b)/(2-0.5)-0.333, 1-F(a,b)/(2-0.5)-0.333, 1]): >  P4 := contourplot(F(a,b), a=0.1 .. 0.5, b=0.1 .. 0.5,                   color="DarkGreen",contours=5): >  display(P3,         transform((a,b,c)->[a,b,1e-2])(P4),         plot3d(0, a=0.1 .. 0.5, b=0.1 .. 0.5,                color="yellow",style=surface),         labels=["x","y","z"], orientation=[30,75,0]);

Download MAXR_surfcontdat_pinkblue.mw

Or perhaps you want pink->something else, as it descends.

Download MAXR_surfcontdat_pinkwhite.mw

@MAXR You're not being completely clear.

If you mean that you want a coloring that goes from pink to blue in a graded manner (say, as a vertical linear gradient, as the "z"-value changes), then you should state that explicitly.

Is that what you want?

note. A few releases after your Maple 17 there was added a `colorscheme` option to do that easily and flexibly right in the `plot3d' call. But I can adjust the 3-component RGB formulas above to do pink->blue instead of white->blue.

@Ronan Sorry I was not clear.

What I meant to convey was that I think it would be more beneficial longterm if you wrote the procedures directly in plaintext files, instead of writing them in the GUI and exporting as plaintext.

This came up in an earlier Question thread, in which Joe Riel & I listed off some benefits; revision control, syntax highlighting in 3rd party text editors. I could also mention: greater safety from .mw saving corruption, protection from save issues. Some editors also allow escaped system commands while open; I execute scripts that build my .mla's straight from my vim editor, and I suspect Joe does similar from his Maple-mode emacs, and I expect some others do similarly from Eclipse.

@Ronan I think that you should write all these procedures in plaintext 1D Maple Notation, not 2D Input.

If you are using Maple 2022 then the (new) default is adaptive=geometric, which for your example may not produce curves as close to the x-axis near the all the roots.

The result is somewhat better for this example in Maple 2022 if you supply the option,
    adaptive=true
in that plot call.

Try it like this,
   plot(abs(sin(x)/x), x=-2*Pi..10*Pi, adaptive=true, numpoints=400);
if you are using Maple 2022.