-
```
What steps will reproduce the problem?
1. Go through tutorial with batch file
2.
3.
What is the expected output? What do you see instead?
C:\Users\jjmarti1\tutorial>c:\Tools\xspec\bin\xspec.bat …
-
When having a set of XSLT files, it may make sense to have a corresponding set of XSpec files, one for each XSLT file. The current command line interface of `xspec.sh` offers no support for this.
A…
-
* BXA version: 4.1.1
* UltraNest version: 3.5.7
* Python version: 3.8.17
* Xspec or Sherpa and version: 12.13.0c (Xspec),
* Operating System: MacOS Ventura 13.5
### Description
I tried to i…
-
Run a string search on the XProc here, for `http://www.jenitennison.com/xslt/xspec/`
https://github.com/xspec/xspec/blob/master/src/harnesses/harness-lib.xpl, and find three hits,
https://github.…
-
# User Story:
As a NIST OSCAL developer, in order to have confidence in Metaschema unit and integration tests with the least amount of effort and highest level of transparency, I want to have the C…
-
```
What steps will reproduce the problem?
1. Go through tutorial with batch file
2.
3.
What is the expected output? What do you see instead?
C:\Users\jjmarti1\tutorial>c:\Tools\xspec\bin\xspec.bat …
-
I forgot to check that the sherpa.astro.utils.xspec code works with recent updates to the XSPEC code. It looks like `model_to_compiled` needs to change - for FORTRAN code - from the
void name_…
-
Note that the output of XSPEC models can be changed by external functions (mainly `set_xsxset`, `set_xsabud`, `set_xsxsect`), which makes cacheing their values "difficult".
-
Is this package still considered experimental? I would really like to switch astromodels over to this and have a common place to work on this as xspec continues to be a huge technical debt.
-
As reported by @AirQuick in #28, when the code coverage option is run for XQuery it doesn't work. @AirQuick reported this:
> I tested `-q -c` (XQuery + coverage) with [xspec-focus-1.xspec](https://…