#875 Workflow - how to support ATLAS

Stable_(v3.10.x)
closed
5
2013-01-14
2012-12-05
No

Hi,

a few additional questions to https://sourceforge.net/tracker/?func=detail&atid=379483&aid=3585712&group_id=23725

What is recommended workflow when deploying applications linked with ATLAS?

Example: Experiment documentation requires source code. Complete ATLAS tarball is not the answer, you can only guess whether you run the same kernel.
Example: Virtual machines are notoriously known to vary performance. ATLAS often refuses to build. You may want to gather more optimization runs.
Example: After initial setup, it is expensive or even impossible to stop all work on the machine to rebuild ATLAS and dependent programs.
Example: Debugging/audit/certification/dumb policy/status report requires builds with and without debuginfo (gcc -g, maybe -O0).
Example: Some free/open source license demands possibility to request source code, patch and rebuild. Hard to satisfy if you do not know, which source corresponds to your current binary. (Not that matrix multiplication is going to get redefined.)

What is the right ATLAS way of doing things?

Thank you very much.

Discussion

  • Now I noticed I can comment even a closed thread. Sorry for duplicating.

     
  • >Example: Experiment documentation requires source code. Complete ATLAS tarball is not the answer, you can only guess whether you run the same kernel.

    Well, you can provide the binaries you used as would with a binary-only lib. All kernels are set by the archdefs, so if you used archdefs then all you need do is specify that and the version of the lib you used. You can also make your own archdefs.

    >Example: Virtual machines are notoriously known to vary performance. ATLAS often refuses to build. You may want to gather more optimization run
    Yes, that is why I do not support installation using a virtual machine. You are free to do it, but I cannot help you with that.
    >Example: After initial setup, it is expensive or even impossible to stop all work on the machine to rebuild ATLAS and dependent programs.

    Do not understand.

    >Example: Some free/open source license demands possibility to request source code, patch and rebuild. Hard to satisfy if you do not know, which source corresponds to your current binary. (Not that matrix multiplication is going to get redefined.)

    The ATLAS tarfile is always the source file, and fully satisfies all licenses. When you use gcc, do you have give all the temporary files generated by configure, or just the gcc tarfile?

    BTW, just 'cause I close a support question, you don't need to open up another request. Unless I mess up, you can always reopen with further questions. I close them when I think I've answered the question, but followups are OK as long as they don't happen again and again.

    Regards,
    Clint

     
    • assigned_to: nobody --> rwhaley
    • status: open --> closed
     
  • Thank you. Using an architectural default: only L1 and L2 cache size is optimized during build? If this is the case, getting a reproducible build should not be very difficult. I was confused by "code generator" previously.

     
    • status: closed --> open
     
    • status: open --> closed