close Warning: Can't synchronize with repository "(default)" (/var/svn/tolp does not appear to be a Subversion repository.). Look in the Trac log for more information.

Opened 17 years ago

Closed 17 years ago

#597 closed defect (fixed)

Tolbase crash graphing series with a lot of data

Reported by: jgarcia Owned by: Jorge
Priority: highest Milestone:
Component: Interface Version: 1.1.6
Severity: critical Keywords:
Cc: Víctor de Buen Remiro

Description

Good morning.

Tolbase crash trying to graph a serie with lot of data.

Serie SubSer(CalInd(Hourly,Hourly),y2001m01d01,y2008m02d10h23i00s00.000);

Sometimes Tolbase can graph this serie but in this case, if you try to change axis serie options and Hourly is selected, applying this change make Tolbase crash

Change History (3)

comment:1 Changed 17 years ago by Jorge

Cc: Víctor de Buen Remiro added
Status: newassigned

This is the piece of code that make tol abort:

if (axisPtr->t1Ptr->nTicks > MAXTICKS) {

fprintf(stderr, "too big, %s major ticks can't be %d\n",

axisPtr->name, axisPtr->t1Ptr->nTicks);

abort();

}

I don't like this way of deal with errors. But now we can no fix inside blt, so we must restrict the number of ticks we can show at the X-axis,

I'll try to make a patch in tcl source in order to prevent the previous situation,

comment:2 Changed 17 years ago by Víctor de Buen Remiro

I think that a convenient solution, and transparent for end user, could be to divide the requested number of ticks T by the maximum period P matching T/P <= MAXTICKS. So, user will see a periodic intervalation o original one. For example if MAXTICKS=20000 and you ask for 80000 hourly ticks, then taking P=4, the chart will show 20000 4-hourly ticks without any problem. In this way, no error message is needed and you should need a monitor with 20000*6 horizontal pixels to view this number of ticks.

comment:3 Changed 17 years ago by Jorge

Resolution: fixed
Status: assignedclosed

the approach proposed by Victor has being applied, and a solution is at CVS

now I want to see that monitor you mentioned!!!!!, jejeje

Note: See TracTickets for help on using tickets.