Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dmaptocdf not working (at least for fitacf files) #211

Open
egthomas opened this issue Jan 21, 2019 · 2 comments
Open

dmaptocdf not working (at least for fitacf files) #211

egthomas opened this issue Jan 21, 2019 · 2 comments

Comments

@egthomas
Copy link
Member

Following these steps (https://github.com/SuperDARN/rst/wiki/Conversion-Tools-(CDF)):

  1. dmaptoskeleton 20181129.cve.fitacf fitacf.skt fitacf.cdfmap
  2. [edit the fitacf.skt file for the correct variable sizes]
  3. /usr/local/cdf/bin/skeletoncdf -cdf 20181129.cve fitacf.skt
  4. dmaptocdf 20181129.cve.fitacf fitacf.cdfmap 20181129.cve.cdf

I'm seeing error codes for either BAD_DIM_INDEX or BAD_DIM_COUNT depending on which version of the CDF library I try using. As far as I can tell, the error is occurring in dmaptocdf when trying to write the ltab array to the output CDF file. This issue was originally identified by Lasse Clausen at UiO.

@egthomas egthomas added the bug label Jan 21, 2019
@egthomas
Copy link
Member Author

After further inspection, I think the issue is that dmaptoskeleton produces a row-majority CDF skeleton table by default while the datamap file format is column-majority (based on my understanding of RFC 0006). Maybe @kkotyk or @mts299 have some insight about this?

@mts299
Copy link
Contributor

mts299 commented Jul 16, 2020

Have we fixed this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants