Re: [PyCAM-devel] [SebKuzminsky/pycam] Error while loading stl file (#102)

[Valerio B. <va...@se...>]

On Mon, 2018-01-01 at 07:21 -0800, John (EBo) David wrote:
> @Ruslan, maybe we should discuss timing tests.  They will take a bit to 
> implement and track, but I have seen them save a project with the timing 
> changed due to a propagated bug.  Do you have anything you use to 
> display and track this type of data?  But the real question is how much 
> time does the overall processing take, and is it worth optimizing the 
> code?


a simple way to keep timings is to run this:

time python3 pycam/run_cli.py [predefined FLOW_SPEC]


this will give times for real,user,sys




> Also, when using numpy I typically set things up to do as little mixing 
> as possible and stick with ndarrays and floats
> 
> On Jan 1 2018 8:07 AM, Ruslan wrote:
> > @ebo, as I can see, there are just few unit tests, and I didn't
> > noticed any performance metrics there. Yes, the main idea of moving
> > towards numpy is because its written in C, however, as mentioned in
> > your links, numpy requires additional step to convert python `list` 
> > to
> > numpy `ndarray`, which, actually, should not be a problem.
> 
> 
> 
> -- 
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly or view it on GitHub:
> https://github.com/SebKuzminsky/pycam/issues/102#issuecomment-354658539