• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. WARNING (OCN-6038) Results dc are not available loading...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 11609
  • 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

WARNING (OCN-6038) Results dc are not available loading OCEAN script

Victor Camacho
Victor Camacho over 4 years ago

Hi,
I'm trying to loading an OCEAN script automatically generated on the ADE-L environment of Cadence virtuoso.
Virtuoso Custom IC Design Environment version IC6.1.8-64b.500.17

I have simplified the ocean script (detailed below between # marks) only to read the "Id dc" result but results seem not to be available on results directory

Message shown on virtuoso terminal:

"job job006 submitted successfully.

WARNING (OCN-6038): Results dc are not available for /../nmos_chara_tb/spectre/schematic/distributed/job006. Use results() for a list of available results"

I have tried to use the "results()" function and this is the information obtained:

results()
("dcOp-dc" "dcOpInfo-info" "dc-dc" "modelParameter-info" "element-info"
    "outputParameter-info" "designParamVals-info" "primitives-info.primitives" "subckts-info.subckts" variables
)

#############################################################################################
simulator( 'spectre )
design(     "/../nmos_chara_tb/spectre/schematic/netlist/netlist")
resultsDir( "/../nmos_chara_tb/spectre/schematic" )
modelFile(
    '("/home/data/pdk/eval/tsmc40nm_cv1p6msp010_001-oav10a/cds/tsmcN40/../models/spectre/toplevel.scs" "top_tt")
)
definitionFile(
    "/../projects/40nmBCD/save_op.scs"
)
analysis('dc ?saveOppoint t  ?dev "/V2"  ?param "dc"  
        ?start "0"  ?stop "3.3"  ?lin "100"  )
desVar(      "length" 550n    )
desVar(      "width" 400n    )
envOption(
    'analysisOrder  list("dc")
)
temp( 27 )
run()
Id = getData("M0:id" ?result "dc")
#############################################################################################

Thanks for the support,
Regards,
Victor.

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago

    Hi Victor,

    It appears that you're running in distributed mode, so the issue is that the run() function doesn't wait for the job to complete, so the getData() is trying to run immediately after the simulation starts. Probably by the time you looked with results() it was OK.

    You can either do:

    job=run()
    wait(job)

    or:

    run(?block t)

    It's possible you might need to use openResults(job) afterwards, but I think that may not be necessary...

    If you have further issues after doing this, please contact customer support - I had some mild challenges with trying to test this, but that's probably just an issue with my local setup.

    Andrew

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • Victor Camacho
    Victor Camacho over 4 years ago in reply to Andrew Beckett

    Hi Andrew,
    Thanks for  your reply. You are right, even running in local in that way job is not completed yet when results are used by the rest of the script.
    I've tried the first choice using "wait" function but it doesn't run because only waits until job is submitted.
    However I've split the *.ocn file into 2 separates files in order to execute simulation first and results analysis and plotting later, and waiting after job is completed execution is ok.
    So I think it will be ok for future uses of these functions.
    Regards,
    Victor.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago in reply to Victor Camacho

    If you were using "command line" distributed mode, then I don't think it can wait for the job to complete because it doesn't know - there's no integration to be able to recognise when the job had completed (it would need to be able to interact with the specific job distribution system).

    Anyway, glad you found a way forward.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information