Stats

Locked Locked
Replies 0
Subscribers 143
Views 461
Members are here 0

This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ADE Assembler Output CSV export using SKILL - Database doesn't update after finished simulation

Hi there,

I am working on a SKILL based tool to easily export certain ADE Assembler outputs as a CSV table, which are then automatically validated using a Python script.

Unfortunately, the code only works after pressing the "Plot all" button. As this extra step is annoying and I don't want to open ViVA, I'm asking for help.
It seems that the database used by my code won't be updated without pressing the "Plot all" button...

I'm currently using the following code section:

histories = axlGetHistoryOutputs(session history_entry ?testName test_name)
data_to_export = nil
foreach(history histories
    println(history~>uniqueName)
    foreach(output history
        when( output~>uniqueName==maeGetVar("xxx_EXPRESSION")
            if( getq( output signal) then
                data_to_export = VT( getq( output signal))
                ;println("xxx_EXPRESSION is a time signal.")    
            else if( getq( output expression) then
                data_to_export = eval( getq( output expression))
                ;println("xxx_EXPRESSION is an expression.")    
                else
                    println("Error: xxx_EXPRESSION not allowed.")
                    return()
                );if
            );if
        );when 
    );foreach
);foreach
if(data_to_export then
    unless( outfile_name = maeGetVar( "xxx_FILENAME" ) outfile_name="dummy_name")
    csv_file_path = sprintf(nil, "./xxx/%s.csv", outfile_name)
    awvSaveToCSV(data_to_export csv_file_path)
else    
    println("Error: xxx_EXPRESSION not found...")
    return()
);if

Best regards and thanks for your help!

Alex

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.